Triple

T1514731
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam Metro network E32093 entity
Predicate hasLine P35 FINISHED
Object Metro Line 51 E113961 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: Metro Line 51 | Statement: [Amsterdam Metro network, hasLine, Metro Line 51]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Metro Line 51
Context triple: [Amsterdam Metro network, hasLine, Metro Line 51]
  • A. Metro line 51 chosen
    Metro line 51 is a former hybrid metro/light rail line in Amsterdam that connected the city center with the southern suburbs, including Amsterdam Zuid.
  • B. Metro Line 6
    Metro Line 6 is a line of the Mexico City Metro system that serves the northern part of the city, including the Gustavo A. Madero borough.
  • C. Metro line 50
    Metro line 50 is a rapid transit line in Amsterdam that runs in an east–west arc connecting several major residential and business districts without passing through the historic city center.
  • D. Metro line 52
    Metro line 52 is Amsterdam’s North–South metro line, connecting the city’s northern and southern districts via the city center and major hubs like Amsterdam Zuid.
  • E. Metro Line 3
    Metro Line 3 is a major Mexico City Metro route that runs north–south across the city, connecting key residential and commercial areas including the Gustavo A. Madero borough.
  • 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_69a885e8caf88190a5fbb6159ce87786 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a907da75388190bfbdbedbd46adbdc completed March 5, 2026, 4:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad294b16e481908a0b3cf7fd774caa completed March 8, 2026, 7:46 a.m.
Created at: March 4, 2026, 7:26 p.m.