Triple

T21032089
Position Surface form Disambiguated ID Type / Status
Subject Parlement of Bordeaux E518088 entity
Predicate hasJurisdictionOver P808 FINISHED
Object Agenais 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: Agenais | Statement: [Parlement of Bordeaux, hasJurisdictionOver, Agenais]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Agenais
Context triple: [Parlement of Bordeaux, hasJurisdictionOver, Agenais]
  • A. Agenais chosen
    Agenais refers to the inhabitants or natives of Agen, a historic town in southwestern France.
  • B. Aiginio
    Aiginio is a town in northern Greece that serves as a local center within the Pieria regional unit, known for its agricultural surroundings and proximity to the Thermaic Gulf.
  • C. Dainava
    Dainava is a historical region in the territory of present-day Lithuania and northeastern Poland, traditionally associated with the Baltic Yotvingian and Lithuanian tribes.
  • D. Aidēs
    Aidēs is an alternate name for Hades, the ancient Greek god who rules the underworld and the realm of the dead.
  • E. Lazdona
    Lazdona is a settlement in eastern Latvia located within Madona Municipality.
  • 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_69e0b503275c8190afd9a163f997c709 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc82b5348190b449d59e6cada9de completed April 21, 2026, 4:26 a.m.
Created at: April 16, 2026, 1:55 p.m.