Triple
T37770245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star-Spangled Comics |
E941525
|
entity |
| Predicate | featuredSuperhero |
P36250
|
FINISHED |
| Object | Star-Spangled Kid |
E447224
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Star-Spangled Kid | Statement: [Star-Spangled Comics, featuredSuperhero, Star-Spangled Kid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredSuperhero Context triple: [Star-Spangled Comics, featuredSuperhero, Star-Spangled Kid]
-
A.
featuresCharacterWithSuperpowers
Indicates that the subject includes or portrays a character who possesses superhuman abilities or powers.
-
B.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
-
C.
superheroStatus
Indicates that an entity possesses the qualities, role, or designation of being a superhero, such as having heroic abilities, identity, or status.
-
D.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
E.
featuresHero
chosen
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f17afeec81908309e8019fe480c3 |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.