Triple
T13698175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Engativá |
E328442
|
entity |
| Predicate | episcopalSee |
P2276
|
FINISHED |
| Object | Engativá |
E503882
|
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: Engativá | Statement: [Diocese of Engativá, episcopalSee, Engativá]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Engativá Context triple: [Diocese of Engativá, episcopalSee, Engativá]
-
A.
Engativá
chosen
Engativá is a locality in the northwestern part of Bogotá, Colombia, characterized by dense residential areas, commercial zones, and significant transport infrastructure.
-
B.
Ututo
Ututo is an Argentine GNU/Linux distribution notable for being one of the first fully free systems endorsed by the Free Software Foundation.
-
C.
Meya
Meya is a variant form of the given name Maya, often used as a feminine personal name.
-
D.
Enenga
Enenga is a dialect of the Myene language spoken by communities in Gabon.
-
E.
Engti
Engti is one of the traditional clans of the Karbi people, an indigenous ethnic group primarily inhabiting the Karbi Anglong region of Assam in Northeast India.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d4f35888190b2c3df62bde1ce6e |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.