Triple
T26848183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Norma |
E675981
|
entity |
| Predicate | accessByTrainVia |
P56141
|
FINISHED |
| Object | Modane railway station |
—
|
NE NERFINISHED |
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: Modane railway station | Statement: [La Norma, accessByTrainVia, Modane railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessByTrainVia Context triple: [La Norma, accessByTrainVia, Modane railway station]
-
A.
railwayAccess
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
B.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
C.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
D.
accessibleFromStation
chosen
Indicates that a location or facility can be reached directly or conveniently starting from a given station.
-
E.
accessibleByPublicTransport
Indicates that a location or entity can be reached using public transportation services such as buses, trains, or trams.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 5:14 a.m.