Triple
T20820688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Man armor |
E512563
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Mark I |
—
|
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 | Statement: [Iron Man armor, hasVariant, Mark I]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mark I Context triple: [Iron Man armor, hasVariant, Mark I]
-
A.
Mark I
chosen
Mark I is the first crude, improvised Iron Man armor suit built by Tony Stark in captivity, serving as the prototype for all subsequent Iron Man armors.
-
B.
Mark I
Mark I is a General Electric-designed boiling water reactor containment system characterized by a compact, pressure-suppression torus configuration used in several nuclear power plants worldwide.
-
C.
Mark I tank
The Mark I tank was the world’s first operational armored fighting vehicle, introduced by Britain during World War I to break the stalemate of trench warfare.
-
D.
Mark-1
Mark-1 is a Jaeger classification used in the Pacific Rim universe to denote the earliest generation of giant human-piloted combat robots like Coyote Tango.
-
E.
Mark II
Mark II is Tony Stark’s early silver-colored Iron Man armor prototype that served as the basis for later, more advanced suits.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 12:41 p.m.