Triple

T8952591
Position Surface form Disambiguated ID Type / Status
Subject Lattrop E213389 entity
Predicate partOf P40 FINISHED
Object Twente E87641 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: Twente | Statement: [Lattrop, partOf, Twente]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Twente
Context triple: [Lattrop, partOf, Twente]
  • A. Twente chosen
    Twente is a historical and cultural region in the eastern Netherlands known for its rural landscapes, industrial heritage, and cities such as Enschede and Hengelo.
  • B. FC Twente
    FC Twente is a professional football club from Enschede in the Netherlands, known for competing in the Eredivisie and winning the Dutch league title in 2010.
  • C. SC Heerenveen
    SC Heerenveen is a Dutch professional football club based in Heerenveen, known for competing in the Eredivisie and developing young talent.
  • D. AZ Alkmaar
    AZ Alkmaar is a Dutch professional football club based in Alkmaar, known for competing in the Eredivisie and developing talented players for top European leagues.
  • E. FC Utrecht
    FC Utrecht is a professional Dutch football club based in Utrecht that competes in the Eredivisie and is regarded as one of the country’s prominent teams.
  • 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_69ca8399ad2081909f8fa41d4314c215 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc670dc0c88190b1f59e96ad88e4ee completed April 1, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc93ed3308190a39069d7b7d4ea3d completed April 3, 2026, 2:05 p.m.
Created at: March 30, 2026, 6:59 p.m.