Triple
T3860565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark-3 |
E90124
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | Mark-4 |
E370348
|
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-4 | Statement: [Mark-3, followedBy, Mark-4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mark-4 Context triple: [Mark-3, followedBy, Mark-4]
-
A.
Mark-4
chosen
Mark-4 is a fourth-generation Jaeger classification used in the Pacific Rim universe, denoting advanced combat robots like Crimson Typhoon.
-
B.
Mark-3
Mark-3 is the third-generation Jaeger class to which the iconic mech Gipsy Danger belongs in the Pacific Rim universe.
-
C.
Mark-5
Mark-5 is a top-tier generation of Jaeger models in the Pacific Rim universe, known for its advanced technology and superior combat performance against kaiju.
-
D.
Mark-6
Mark-6 is the sixth-generation Jaeger model classification used in the Pacific Rim universe, exemplified by the advanced mech Gipsy Avenger.
-
E.
Mark III
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.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec212a1c8190aba6311630c3fd3e |
completed | March 9, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51c7d99208190baee9830cc448eee |
completed | March 14, 2026, 8:29 a.m. |
Created at: March 9, 2026, 3:19 p.m.