Triple

T14185691
Position Surface form Disambiguated ID Type / Status
Subject Rotterdam Metro E351568 entity
Predicate hasLine P35 FINISHED
Object Line E
Line E is a major Rotterdam Metro route that connects the city with The Hague as part of the RandstadRail network in the Netherlands.
 E1086252 NE FINISHED

How this triple was built (4 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: Line E | Statement: [Rotterdam Metro, hasLine, Line E]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Line E
Context triple: [Rotterdam Metro, hasLine, Line E]
  • A. Line E
    Line E is one of the lines of the Buenos Aires Underground, serving as a key rapid transit route across parts of the Argentine capital.
  • B. Line E
    Line E is one of the routes of the Strasbourg tramway network, providing urban light-rail transit service across parts of Strasbourg and its surrounding areas.
  • C. Line E
    Line E is a light rail route of the Porto Metro system in Portugal, connecting key areas of the metropolitan region.
  • D. Line L
    Line L is a cable car line of the Medellín Metro system that serves hillside neighborhoods by connecting them to the main urban transit network.
  • E. E line
    The E line was a streetcar route in the historic Los Angeles Railway system that served local passengers in Los Angeles during the early to mid-20th century.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Line E
Triple: [Rotterdam Metro, hasLine, Line E]
Generated description
Line E is a major Rotterdam Metro route that connects the city with The Hague as part of the RandstadRail network in the Netherlands.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Line E
Target entity description: Line E is a major Rotterdam Metro route that connects the city with The Hague as part of the RandstadRail network in the Netherlands.
  • A. Line E
    Line E is one of the lines of the Buenos Aires Underground, serving as a key rapid transit route across parts of the Argentine capital.
  • B. Line E
    Line E is one of the routes of the Strasbourg tramway network, providing urban light-rail transit service across parts of Strasbourg and its surrounding areas.
  • C. Line E
    Line E is a light rail route of the Porto Metro system in Portugal, connecting key areas of the metropolitan region.
  • D. Line L
    Line L is a cable car line of the Medellín Metro system that serves hillside neighborhoods by connecting them to the main urban transit network.
  • E. E line
    The E line was a streetcar route in the historic Los Angeles Railway system that served local passengers in Los Angeles during the early to mid-20th century.
  • F. None of above. chosen

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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61cd5778819092a03597bcdcc182 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd19433dc08190b4d2f1aef1b2d67d completed May 7, 2026, 10:59 p.m.
NEDg Description generation batch_69fd1ad65b608190b325c82347a3d8b3 completed May 7, 2026, 11:05 p.m.
NED2 Entity disambiguation (via description) batch_69fd1b68e8288190a9e9e3d855ed2719 completed May 7, 2026, 11:08 p.m.
Created at: April 10, 2026, 1:03 a.m.