Triple
T7119914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Highspeed |
E165921
|
entity |
| Predicate | safetySystem |
P840
|
FINISHED |
| Object | TVM-430 |
E386838
|
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: TVM-430 | Statement: [Southeastern Highspeed, safetySystem, TVM-430]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TVM-430 Context triple: [Southeastern Highspeed, safetySystem, TVM-430]
-
A.
TVM-430
chosen
TVM-430 is a modern in-cab railway signaling and train protection system used on high-speed lines such as the French TGV network.
-
B.
TVM-300
TVM-300 is a high-speed railway cab signalling and train control system used on French high-speed lines such as the LGV Nord.
-
C.
Vanguard TV-4
Vanguard TV-4 was the American Vanguard rocket that successfully launched Vanguard 1, one of the earliest artificial Earth satellites, during the early space race.
-
D.
TX-38
TX-38 is a U.S. congressional district in Texas represented in the House of Representatives.
-
E.
TX-4
TX-4 is the commonly used abbreviation for Texas's 4th congressional district in the United States House of Representatives.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61ca6a88190a0eb9f287e3b723c |
completed | March 27, 2026, 8:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c79cc4683c8190b0788a142e93e088 |
completed | March 28, 2026, 9:17 a.m. |
Created at: March 27, 2026, 2:43 p.m.