Triple
T33342205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banzebi |
E853699
|
entity |
| Predicate | closelyAssociatedPeople |
P77482
|
FINISHED |
| Object | Nzebi people |
—
|
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: Nzebi people | Statement: [Banzebi, closelyAssociatedPeople, Nzebi people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyAssociatedPeople Context triple: [Banzebi, closelyAssociatedPeople, Nzebi people]
-
A.
peopleAssociatedWith
chosen
Indicates that there exists some form of connection, involvement, or relationship between the referenced people.
-
B.
worksInCloseRelationshipWith
Indicates a collaborative professional relationship in which two or more entities work together closely and interact frequently to achieve shared goals.
-
C.
closelyInvolvedWith
Indicates a relationship in which one entity is deeply and actively engaged with another’s activities, decisions, or affairs.
-
D.
relatedWorkOfPerson
Indicates that a work (such as a publication, project, or creation) is associated with or produced by a particular person.
-
E.
associatedPersonField
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:34 a.m.