Triple
T28976059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales of Suspense |
E734412
|
entity |
| Predicate | ironManArmorDebut |
P166264
|
FINISHED |
| Object | Mark I armor |
—
|
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: Mark I armor | Statement: [Tales of Suspense, ironManArmorDebut, Mark I armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ironManArmorDebut Context triple: [Tales of Suspense, ironManArmorDebut, Mark I armor]
-
A.
ironManFeatureContinuedIn
Indicates that an Iron Man feature or storyline is continued in another issue, series, or publication.
-
B.
ironmanStreakEndDate
Indicates the date on which an ongoing Ironman streak (a continuous participation or completion sequence) comes to an end.
-
C.
marvelCinematicUniverseDebutFilm
Indicates the film in which an entity (such as a character or actor) first appeared within the Marvel Cinematic Universe.
-
D.
ironmanStreakStartDate
Indicates the date on which an Ironman streak (a continuous sequence of Ironman-related events or completions) begins.
-
E.
airDateOfFirstAppearance
Indicates the calendar date on which an entity (such as a character, show, or episode) was first broadcast or made publicly available.
- F. None of above. chosen
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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:08 a.m.