Triple
T18622465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmande station |
E455188
|
entity |
| Predicate | hasIntercityRole |
P47674
|
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: [Marmande station, hasIntercityRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntercityRole Context triple: [Marmande station, hasIntercityRole, yes]
-
A.
operatesInterCityServices
Indicates that an entity runs or provides transportation services connecting different cities.
-
B.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
hasIntercityPlatforms
chosen
Indicates that a location or station includes platforms designated for intercity train services.
-
D.
hasIntermediateStation
Indicates that a route, journey, or connection includes a station that lies between its starting point and its final destination.
-
E.
hasRailInterchangeFunction
Indicates that something serves as a location or facility where rail lines connect or intersect, allowing passengers or goods to transfer between them.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f020fa08190bd78d72182496b19 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.