Triple

T8281009
Position Surface form Disambiguated ID Type / Status
Subject Grimburgwal E193670 entity
Predicate locatedNear P294 FINISHED
Object Rokin E65569 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: Rokin | Statement: [Grimburgwal, locatedNear, Rokin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rokin
Context triple: [Grimburgwal, locatedNear, Rokin]
  • A. Rokin chosen
    Rokin is a major street and canal in central Amsterdam, known for its historic buildings, shops, and proximity to Dam Square.
  • B. Roden
    Roden is a town in the Dutch province of Drenthe known as a local service and population center within the municipality of Noordenveld.
  • C. Rokkasen
    Rokkasen refers to the group of six celebrated classical Japanese waka poets of the early Heian period, renowned for their exemplary and influential verse.
  • D. Rayak
    Rayak is a town in Lebanon known historically for its strategic railway junction and air base in the Bekaa Valley.
  • E. Ringlow
    Ringlow is a locality in Sheffield, South Yorkshire, England, situated in the countryside near the upper reaches of the Porter Brook.
  • 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_69ca82e217a48190880695635c44b2ed completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb79ee66e48190af7058b14f3daac9 completed March 31, 2026, 7:38 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd6877b8e481908ec1e0b91a5276f6 completed April 1, 2026, 6:48 p.m.
Created at: March 30, 2026, 5:51 p.m.