Triple
T24181760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oguaa Fetu Afahye |
E599443
|
entity |
| Predicate | chiefPatron |
P44585
|
FINISHED |
| Object | Omanhen of Oguaa Traditional Area |
—
|
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: Omanhen of Oguaa Traditional Area | Statement: [Oguaa Fetu Afahye, chiefPatron, Omanhen of Oguaa Traditional Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefPatron Context triple: [Oguaa Fetu Afahye, chiefPatron, Omanhen of Oguaa Traditional Area]
-
A.
primaryPatron
chosen
Indicates that one entity serves as the main or chief supporter, sponsor, or benefactor of another entity.
-
B.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
C.
chiefSaintOf
Indicates that one entity serves as the principal or primary patron saint associated with another entity (such as a place, group, or institution).
-
D.
patroness
Indicates that a female person supports, sponsors, or acts as a benefactor for someone or something.
-
E.
coPatron
Indicates a relationship where two or more entities share joint responsibility or role as patrons supporting the same person, group, or endeavor.
- F. None of above.
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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.