Triple

T15864946
Position Surface form Disambiguated ID Type / Status
Subject Linden E384686 entity
Predicate hasStationCode P1289 FINISHED
Object Linden E384686 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: Linden | Statement: [Linden, hasStationCode, Linden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Linden
Context triple: [Linden, hasStationCode, Linden]
  • A. Linden
    Linden is a small village in the Dutch province of North Brabant, known for its rural character and location near the Maas River.
  • B. Linden
    Linden is a small city in Marengo County, Alabama, serving as the county seat and known for its rural Southern character.
  • C. Linden
    Linden is a small village in the City of Blue Mountains in New South Wales, Australia, known for its bushland setting and proximity to scenic mountain lookouts and walking tracks.
  • D. Linden chosen
    Linden is a Chicago Transit Authority rapid transit station that serves as the northern terminal of the Purple Line in Wilmette, Illinois.
  • E. Linden
    Linden is a major town in central Guyana known for its bauxite mining industry and location along the Demerara River.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1555e4ee48190a3b27b4ab9bdb1c8 completed April 16, 2026, 9:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa945d9808190a65f5182db341393 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:50 a.m.