Triple

T14185687
Position Surface form Disambiguated ID Type / Status
Subject Rotterdam Metro E351568 entity
Predicate hasLine P35 FINISHED
Object Line A
Line A is one of the main routes of the Rotterdam Metro rapid transit system, serving multiple districts in and around Rotterdam in the Netherlands.
 E1086249 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 A | Statement: [Rotterdam Metro, hasLine, Line A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Line A
Context triple: [Rotterdam Metro, hasLine, Line A]
  • A. Line A
    Line A is a line of the Mexico City Metro system that serves the eastern part of the metropolitan area, connecting central Mexico City with several suburban municipalities.
  • B. Line A
    Line A is the main north–south rapid transit line of the Medellín Metro system in Colombia, serving as its busiest and most central corridor.
  • C. Line A
    Line A is the primary route of the Bilbao tram system, serving key areas of the city with modern light rail service.
  • D. Line A
    Line A is one of the main lines of the Prague Metro, running east–west through the city and serving several central and residential districts.
  • E. Line A
    Line A is one of the main routes of the Porto Metro light rail system in Porto, Portugal, connecting key urban and suburban areas.
  • 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 A
Triple: [Rotterdam Metro, hasLine, Line A]
Generated description
Line A is one of the main routes of the Rotterdam Metro rapid transit system, serving multiple districts in and around Rotterdam in the Netherlands.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Line A
Target entity description: Line A is one of the main routes of the Rotterdam Metro rapid transit system, serving multiple districts in and around Rotterdam in the Netherlands.
  • A. Line A
    Line A is one of the main routes of the Porto Metro light rail system in Porto, Portugal, connecting key urban and suburban areas.
  • B. Line A
    Line A is one of the main lines of the Prague Metro, running east–west through the city and serving several central and residential districts.
  • C. Line A
    Line A is one of the main routes of the Strasbourg tramway network, providing key light-rail transit across the city.
  • D. Line A
    Line A is the main north–south rapid transit line of the Medellín Metro system in Colombia, serving as its busiest and most central corridor.
  • E. Line A
    Line A is the primary route of the Bilbao tram system, serving key areas of the city with modern light rail service.
  • 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.