Triple
T30821469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Man film series |
E784931
|
entity |
| Predicate | connectedUniverse |
P47705
|
FINISHED |
| Object | Infinity Saga |
—
|
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: Infinity Saga | Statement: [Iron Man film series, connectedUniverse, Infinity Saga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedUniverse Context triple: [Iron Man film series, connectedUniverse, Infinity Saga]
-
A.
associatedUniverse
Indicates that one entity is linked or belongs to a particular universe, realm, or overarching world context.
-
B.
inUniverse
chosen
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
C.
inUniverseStar
Indicates that a star exists or is located within a particular fictional or defined universe.
-
D.
componentUniverse
Indicates that one entity is the complete set or universe of components from which the other entity’s parts or elements are drawn.
-
E.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 29, 2026, 8:44 p.m.