Triple
T31516360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironheart |
E804082
|
entity |
| Predicate | inUniverseSuccessorTo |
P78292
|
FINISHED |
| Object | Iron Man |
—
|
NE NERFINISHED |
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: Iron Man | Statement: [Ironheart, inUniverseSuccessorTo, Iron Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseSuccessorTo Context triple: [Ironheart, inUniverseSuccessorTo, Iron Man]
-
A.
inUniverseSuccessor
chosen
Indicates that one entity is the next or following entity in sequence within a particular fictional or defined universe or continuity.
-
B.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
C.
isTemporarySuccessorOf
Indicates that one entity serves as a short-term or interim replacement for another entity in a given role or position.
-
D.
successorInstanceOf
Indicates that one entity is a later or updated instance of another, preserving a continuity or versioned succession between them.
-
E.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
- F. None of above.
Provenance (3 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 30, 2026, 9:53 p.m.