Triple
T8445165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z 57000 RER NG |
E199654
|
entity |
| Predicate | network |
P2637
|
FINISHED |
| Object | RER E |
E153469
|
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 E | Statement: [Z 57000 RER NG, network, RER E]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RER E Context triple: [Z 57000 RER NG, network, RER E]
-
A.
RER A
RER A is one of the main lines of the Paris regional express network, carrying large volumes of commuters and travelers between central Paris and its suburbs.
-
B.
RER D
RER D is one of the main lines of the Paris regional express network (RER), connecting northern and southern suburbs through central Paris.
-
C.
RER C
RER C is a major line of the Paris regional express rail network that connects central Paris with several suburbs and key destinations, including access to Orly Airport.
-
D.
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.
-
E.
RER line E
chosen
RER line E is a Paris regional express railway line connecting central Paris with eastern suburbs such as Gagny.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3138ee08190918cd82adbe2d9a1 |
completed | March 31, 2026, 3:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39b528f08190a0627cb17a0ffef9 |
completed | April 2, 2026, 9:41 a.m. |
Created at: March 30, 2026, 6:09 p.m.