Triple
T25370898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villeneuve-le-Roi |
E632927
|
entity |
| Predicate | locatedOnTransport |
P86982
|
FINISHED |
| Object | RER line C |
—
|
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: RER line C | Statement: [Villeneuve-le-Roi, locatedOnTransport, RER line C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnTransport Context triple: [Villeneuve-le-Roi, locatedOnTransport, RER line C]
-
A.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
B.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
C.
onboardLocation
Indicates that one entity is located on or within a vehicle, vessel, or other conveyance associated with another entity.
-
D.
situatedOnTransportRoute
chosen
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
E.
locatedOnReservation
Indicates that an entity is situated within the geographic boundaries of a designated reservation.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 21, 2026, 1:38 p.m.