Triple

T21319386
Position Surface form Disambiguated ID Type / Status
Subject Dijle E525569 entity
Predicate alternativeName P39 FINISHED
Object Dyle 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: Dyle | Statement: [Dijle, alternativeName, Dyle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dyle
Context triple: [Dijle, alternativeName, Dyle]
  • A. Dyle chosen
    Dyle is a river in central Belgium that flows through cities such as Leuven and Mechelen before joining the Rupel.
  • B. Elwell
    Elwell is a masculine given name of English origin, historically used in the United States and associated with figures such as military officer Elwell Stephen Otis.
  • C. Dorodoche
    Dorodoche is a minor figure in Greek mythology known primarily as the wife of Icarius.
  • D. Longfield
    Longfield is a village and civil parish in the borough of Dartford in north-west Kent, England, known for its commuter links to London and surrounding rural setting.
  • E. Norlane
    Norlane is a residential suburb in the northern part of Geelong, Victoria, Australia, known for its post-war housing and proximity to industrial and port areas.
  • 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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e77ecf12248190bb4172ad7416775e completed April 21, 2026, 1:42 p.m.
Created at: April 16, 2026, 4:38 p.m.