Triple
T26237568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaties of Benin |
E656211
|
entity |
| Predicate | mayBeDepositedWith |
P163875
|
FINISHED |
| Object | African Union Commission |
—
|
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: African Union Commission | Statement: [Treaties of Benin, mayBeDepositedWith, African Union Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDepositedWith Context triple: [Treaties of Benin, mayBeDepositedWith, African Union Commission]
-
A.
mayBeDepositedWith
chosen
Indicates that one entity is allowed or suitable to be placed, stored, or entrusted with another entity.
-
B.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
C.
hasDepositType
Indicates that an entity is associated with or classified by a particular type of deposit.
-
D.
containsDeposits
Indicates that one entity holds, includes, or has within it one or more deposits associated with another entity.
-
E.
oreDeposit
Indicates the presence or occurrence of a concentrated natural accumulation of ore at or within a specified location or geological context.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 9:02 p.m.