Triple
T20820810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Legion |
E512566
|
entity |
| Predicate | introducedInUniverseYear |
P124238
|
FINISHED |
| Object | post-Battle of New York era |
—
|
LITERAL 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: post-Battle of New York era | Statement: [Iron Legion, introducedInUniverseYear, post-Battle of New York era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInUniverseYear Context triple: [Iron Legion, introducedInUniverseYear, post-Battle of New York era]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
firstAppearanceUniverse
Indicates the universe or continuity in which an entity makes its first recorded appearance.
-
C.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
D.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
E.
firstAppearanceUniverseEra
chosen
Indicates the specific universe era in which an entity makes its first recorded appearance.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f7a1548190b6ef3f1cfad37c1c |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.