Triple
T26594627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gare de Clamecy |
E667456
|
entity |
| Predicate | isMainRailwayStationFor |
P1071
|
FINISHED |
| Object | Clamecy |
—
|
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: Clamecy | Statement: [Gare de Clamecy, isMainRailwayStationFor, Clamecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainRailwayStationFor Context triple: [Gare de Clamecy, isMainRailwayStationFor, Clamecy]
-
A.
isMainBusStationFor
Indicates that one bus station serves as the primary or central station for a particular area, network, or service.
-
B.
hasRailwayStationOn
Indicates that a railway station is located on or serves a particular railway line, route, or network segment.
-
C.
hasMajorRailwayStation
chosen
Indicates that a place contains or is served by a principal railway station that functions as a major hub for rail transport.
-
D.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
E.
hasRailwayStation
Indicates that a place or location is served by, or contains, a railway station.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:09 a.m.