Triple

T10102453
Position Surface form Disambiguated ID Type / Status
Subject Protestant church of Abbenes E216234 entity
Predicate locatedIn P40 FINISHED
Object Abbenes E40966 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: Abbenes | Statement: [Protestant church of Abbenes, locatedIn, Abbenes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abbenes
Context triple: [Protestant church of Abbenes, locatedIn, Abbenes]
  • A. Abbenes chosen
    Abbenes is a small village in the Dutch province of North Holland, situated within the municipality of Haarlemmermeer.
  • B. Abele
    Abele is a surname most notably associated with Julian Abele, a pioneering African American architect who contributed to the design of many prominent buildings in the early 20th century.
  • C. Argobba
    Argobba is an endangered South Semitic language spoken by the Argobba people in central Ethiopia.
  • D. Abunayyan
    Abunayyan is a prominent Saudi family name associated with influential figures in business and public life in Saudi Arabia.
  • E. Bahdini
    Bahdini is a Northern Kurdish dialect spoken primarily in parts of Turkey and Iraq.
  • 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_69ca83d039f08190b9d10363221c69fb completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd099c21c819097aac4f0f168a2da completed April 2, 2026, 2:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b6dcca848190851f6f1968fe244c completed April 5, 2026, 7:24 p.m.
Created at: March 30, 2026, 9:02 p.m.