Triple

T19379073
Position Surface form Disambiguated ID Type / Status
Subject Ringlijn E484749 entity
Predicate commonName P570 FINISHED
Object Ringlijn NE NERFINISHED

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: Ringlijn | Statement: [Ringlijn, commonName, Ringlijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ringlijn
Context triple: [Ringlijn, commonName, Ringlijn]
  • A. Ringlijn chosen
    Ringlijn is the common name for Amsterdam Metro line 50, a rapid transit route that forms a partial ring around the city.
  • B. Ringbahn
    The Ringbahn is Berlin’s circular urban rail line that encircles the inner city and serves as a major hub for the Berlin S-Bahn network.
  • C. Rjukan Line
    The Rjukan Line was a Norwegian railway line built to serve the industrial town of Rjukan, notably used for transporting chemicals and playing a role in World War II heavy water operations.
  • D. Gribskov Line
    The Gribskov Line is a Danish regional railway line in North Zealand that connects Hillerød with several coastal and rural towns, serving as an important local transport route and tourist line.
  • E. R Line
    The R Line is a New York City Subway service that runs through Brooklyn, Queens, and Manhattan, connecting neighborhoods along a local route in the BMT Broadway Line corridor.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61a5e8e7081908bed3eee1eef4de2 completed April 20, 2026, 12:21 p.m.
Created at: April 10, 2026, 1:35 p.m.