Triple

T4201733
Position Surface form Disambiguated ID Type / Status
Subject Z 20500 E86081 entity
Predicate usedBy P260 FINISHED
Object RER network E68667 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 network | Statement: [Z 20500, usedBy, RER network]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RER network
Context triple: [Z 20500, usedBy, RER network]
  • A. RER network chosen
    The RER network is a rapid transit system of express suburban trains serving Paris and its surrounding metropolitan area, integrating both urban and regional rail services.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. RER line E
    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_69aed93b89f48190a31f6d57c760e42f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af037da30481908106b27a88d59140 completed March 9, 2026, 5:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69be777b514081909832a8a520a7f7d1 completed March 21, 2026, 10:48 a.m.
Created at: March 9, 2026, 3:49 p.m.