Triple

T14561017
Position Surface form Disambiguated ID Type / Status
Subject Kongens Nytorv metro station E341663 entity
Predicate partOf P40 FINISHED
Object Harbour Line (M4) E338242 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: Harbour Line (M4) | Statement: [Kongens Nytorv metro station, partOf, Harbour Line (M4)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Harbour Line (M4)
Context triple: [Kongens Nytorv metro station, partOf, Harbour Line (M4)]
  • A. Harbour Line
    Harbour Line is a major corridor of Mumbai's suburban railway network that connects the city’s eastern waterfront and Navi Mumbai suburbs to key central and southern Mumbai terminals.
  • B. Harbour Line chosen
    Harbour Line is a Copenhagen Metro route that serves areas along the city’s waterfront and harbor districts.
  • C. M4 line
    The M4 line is a rapid transit route of the Istanbul Metro system serving the city’s Asian side.
  • D. M4 line
    The M4 line is a rapid transit route within the Ankara Metro system serving passengers in Turkey’s capital city.
  • E. M44 line
    The M44 line is a rapid transit route within the Istanbul Metro system serving passengers across part of the city’s urban rail network.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb389d0f48190a1d9d69456d1cbe1 completed April 14, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8ac294748190a4bfeed8c5fd9e94 completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:23 a.m.