Triple
T18999325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendôme-Villiers-sur-Loir TGV |
E464902
|
entity |
| Predicate | hasConnectingBusServices |
P39381
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Vendôme-Villiers-sur-Loir TGV, hasConnectingBusServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectingBusServices Context triple: [Vendôme-Villiers-sur-Loir TGV, hasConnectingBusServices, yes]
-
A.
hasBusServices
chosen
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
hasCommuterServices
Indicates that a location or facility provides transportation services specifically intended for regular commuters, such as daily or frequent travelers between home and work or school.
-
C.
hasBusPlatforms
Indicates that a location or facility is equipped with one or more designated platforms for boarding or alighting from buses.
-
D.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
E.
hasBusOperator
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
- F. None of above.
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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d684d37c8190b975f04a47fa7b92 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.