Triple
T3765962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV POS |
E82676
|
entity |
| Predicate | safetySystem |
P840
|
FINISHED |
| Object | KVB |
E194420
|
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: KVB | Statement: [TGV POS, safetySystem, KVB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KVB Context triple: [TGV POS, safetySystem, KVB]
-
A.
KVB
chosen
KVB is a French train protection and automatic speed control system used to enhance the safety of railway operations.
-
B.
KCB
KCB is the post-nominal abbreviation for Knight Commander of the Order of the Bath, a senior British order of chivalry.
-
C.
CBK
CBK is the Central Bank of Kenya, the national monetary authority responsible for issuing currency and formulating and implementing the country’s monetary policy.
-
D.
CBK
CBK is the Central Bank of Kuwait, the country’s primary monetary authority responsible for issuing currency, regulating the banking sector, and formulating monetary policy.
-
E.
VKO
VKO is the IATA airport code for Vnukovo International Airport, one of Moscow’s major international airports in Russia.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfeb52081909c38103beb5dbdcd |
completed | March 8, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4e5221ab08190a3599afbbd5dbc6e |
completed | March 14, 2026, 4:33 a.m. |
Created at: March 8, 2026, 3:35 p.m.