Triple

T6151990
Position Surface form Disambiguated ID Type / Status
Subject Orsay E137224 entity
Predicate servedBy P82 FINISHED
Object RER B line E10905 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 B line | Statement: [Orsay, servedBy, RER B line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RER B line
Context triple: [Orsay, servedBy, RER B line]
  • A. RER B line chosen
    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.
  • B. RER line E
    RER line E is a Paris regional express railway line connecting central Paris with eastern suburbs such as Gagny.
  • C. 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.
  • D. 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.
  • 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_69c008a45d008190832a9e19f5d63406 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05cfcb5cc8190b998e92211810442 completed March 22, 2026, 9:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1360d84e081909ff6c06e3bd54aee completed March 23, 2026, 12:46 p.m.
Created at: March 22, 2026, 4:16 p.m.