Triple

T23554262
Position Surface form Disambiguated ID Type / Status
Subject Farsta E578135 entity
Predicate servedByMetroLine P6301 FINISHED
Object Green line 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: Green line | Statement: [Farsta, servedByMetroLine, Green line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Green line
Context triple: [Farsta, servedByMetroLine, Green line]
  • A. Green line chosen
    The Green line is one of the main color-coded routes in the Stockholm metro system, serving numerous central and suburban stations across the city.
  • B. Green line
    The Green line is a major rapid transit route on the Barcelona Metro system, serving numerous central and outlying neighborhoods across the city.
  • C. green line
    The green line refers to the Zamoskvoretskaya Line, one of the busiest and oldest lines of the Moscow Metro system.
  • D. Blue line
    The Blue line is one of the main lines of the Stockholm metro system, connecting central Stockholm with several northern and western suburbs.
  • E. Red line
    The Red line is one of the main color-coded routes of the Stockholm metro system, serving numerous central and suburban stations across the city.
  • 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_69e245fa93448190919cb04534560542 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1aed17fc881908b45dcde14790d42 completed April 29, 2026, 7:10 a.m.
Created at: April 17, 2026, 6:12 p.m.