Triple
T8304289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TER Grand Est services |
E194422
|
entity |
| Predicate | partOfNetwork |
P840
|
FINISHED |
| Object | TER |
E41185
|
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: TER | Statement: [TER Grand Est services, partOfNetwork, TER]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TER Context triple: [TER Grand Est services, partOfNetwork, TER]
-
A.
TER
TER is the IATA airport code for Lajes Airport on Terceira Island in the Azores, Portugal.
-
B.
TER
chosen
TER is a network of regional express trains in France that provides local passenger rail services across various regions.
-
C.
Ter
The Ter is a river in northeastern Catalonia, Spain, that flows through cities such as Girona before emptying into the Mediterranean Sea.
-
D.
TR
TR is the postcode area covering Truro and much of Cornwall in southwest England.
-
E.
TR
TR is the two-letter ISO 3166-1 alpha-2 country code assigned to Turkey for international standardization and referencing.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8b9f6081909100d1da8a078616 |
completed | March 31, 2026, 7:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd9545ffc48190869906b02692b873 |
completed | April 1, 2026, 9:59 p.m. |
Created at: March 30, 2026, 5:53 p.m.