Triple
T14878233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark II |
E349924
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | Mark III |
E350875
|
NE 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: Mark III | Statement: [Mark II, followedBy, Mark III]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mark III Context triple: [Mark II, followedBy, Mark III]
-
A.
Mark III
chosen
Mark III is one of Tony Stark’s early Iron Man armor suits, recognized for refining his initial design into a more advanced, weaponized, and iconic red-and-gold configuration.
-
B.
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.
-
C.
Mark-3
Mark-3 is the third-generation Jaeger class to which the iconic mech Gipsy Danger belongs in the Pacific Rim universe.
-
D.
Mark-4
Mark-4 is a fourth-generation Jaeger classification used in the Pacific Rim universe, denoting advanced combat robots like Crimson Typhoon.
-
E.
Mark VIII
The Mark VIII is a British World War I–era torpedo that became one of the Royal Navy’s standard submarine-launched torpedoes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b5670108190b41ef95dc318be60 |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 1:55 a.m.