Triple
T5313691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 2 coaching stock |
E119092
|
entity |
| Predicate | subclass |
P1244
|
FINISHED |
| Object | Mark 2D |
E119092
|
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 2D | Statement: [Mark 2 coaching stock, subclass, Mark 2D]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mark 2D Context triple: [Mark 2 coaching stock, subclass, Mark 2D]
-
A.
MK 2
MK 2 is the small natural satellite orbiting the distant dwarf planet Makemake in the Kuiper Belt.
-
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-4
Mark-4 is a fourth-generation Jaeger classification used in the Pacific Rim universe, denoting advanced combat robots like Crimson Typhoon.
-
D.
Mark 2 coaching stock
chosen
Mark 2 coaching stock is a class of British Rail passenger carriages introduced in the 1960s, widely used across the UK rail network for intercity and regional services.
-
E.
Count of Mark
Count of Mark was a historic noble title associated with the County of Mark in the Holy Roman Empire, often held by rulers who also governed larger German principalities such as Brandenburg and Prussia.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd854d947081909e51b27e40940580 |
completed | March 20, 2026, 5:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf1106ef9c8190811f7b70e784c962 |
completed | March 21, 2026, 9:43 p.m. |
Created at: March 20, 2026, 1:54 p.m.