Triple
T17070934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCF TER |
E414215
|
entity |
| Predicate | additionalModeOfTransport |
P70708
|
FINISHED |
| Object | bus |
—
|
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: bus | Statement: [SNCF TER, additionalModeOfTransport, bus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalModeOfTransport Context triple: [SNCF TER, additionalModeOfTransport, bus]
-
A.
hasSecondaryTransportationMode
chosen
Indicates that an entity is associated with an additional, non-primary mode of transportation it can use or provide.
-
B.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
C.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
transportContribution
Indicates that an entity contributes resources, effort, or support toward the transportation of something or someone.
-
E.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc0982c8190916f9905ddb5e575 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.