Triple
T31608485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gare de Lisieux |
E806558
|
entity |
| Predicate | servesRailTrafficType |
P196410
|
FINISHED |
| Object | passenger |
—
|
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: passenger | Statement: [Gare de Lisieux, servesRailTrafficType, passenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRailTrafficType Context triple: [Gare de Lisieux, servesRailTrafficType, passenger]
-
A.
hasRailwayTrafficType
chosen
Indicates the type or category of railway traffic that operates on or is associated with a given railway infrastructure or service.
-
B.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
C.
servesRailTrafficBetween
Indicates that something (typically a rail line, service, or facility) provides rail transportation connecting two or more locations.
-
D.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
E.
servesRailCorridor
Indicates that something (such as a service, facility, or operation) provides service to or operates along a specific rail corridor.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 30, 2026, 10:35 p.m.