Triple
T16066528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orly area |
E389745
|
entity |
| Predicate | servedBy |
P82
|
FINISHED |
| Object | RER C line |
E601935
|
NE 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: RER C line | Statement: [Orly area, servedBy, RER C line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RER C line Context triple: [Orly area, servedBy, RER C line]
-
A.
RER Line C
chosen
RER Line C is a major commuter rail line in the Paris RER network, running along the Seine and serving numerous suburbs and key destinations in the Île-de-France region.
-
B.
RER B line
The RER B line is a major Paris regional express railway line that connects central Paris with key northern and southern suburbs, including Charles de Gaulle Airport.
-
C.
RER line E
RER line E is a Paris regional express railway line connecting central Paris with eastern suburbs such as Gagny.
-
D.
RER line D
RER line D is one of the main lines of the Paris RER suburban rail network, running north–south through central Paris and serving numerous suburbs across the Île-de-France region.
-
E.
RER Vaud
RER Vaud is a regional express rail network in the canton of Vaud, Switzerland, providing frequent commuter and regional train services connecting local towns and cities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1837ca628819081dfc439fe322d58 |
completed | April 17, 2026, 12:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff299f14c8190a5f88754b6a78b1f |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 4:57 a.m.