Triple

T30063224
Position Surface form Disambiguated ID Type / Status
Subject Javel–André Citroën E763951 entity
Predicate hasService P182 FINISHED
Object RER C suburban trains
RER C suburban trains are regional express rail services in the Paris metropolitan area that connect central Paris with numerous suburbs along the Seine and beyond.
E1909968 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 suburban trains | Statement: [Javel–André Citroën, hasService, RER C suburban trains]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RER C suburban trains
Triple: [Javel–André Citroën, hasService, RER C suburban trains]
Generated description
RER C suburban trains are regional express rail services in the Paris metropolitan area that connect central Paris with numerous suburbs along the Seine and beyond.

Provenance (5 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_69f2247221388190a13a22c47094a0ef completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67ca4dc388190a6f3cf48f2fad819 completed May 2, 2026, 10:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a277bf9786881909950b75f27bbb3bd completed June 9, 2026, 2:35 a.m.
NEDg Description generation batch_6a277d09f32c8190a75331cdfafd9456 completed June 9, 2026, 2:40 a.m.
NED2 Entity disambiguation (via description) batch_6a277dc406308190a2e54214a8851a14 completed June 9, 2026, 2:43 a.m.
Created at: April 29, 2026, 6:58 p.m.