Triple
T25253932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Union passport |
E633116
|
entity |
| Predicate | intendedHolder |
P160907
|
FINISHED |
| Object | citizens of African Union member states |
—
|
LITERAL 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: citizens of African Union member states | Statement: [African Union passport, intendedHolder, citizens of African Union member states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedHolder Context triple: [African Union passport, intendedHolder, citizens of African Union member states]
-
A.
firstHolderParty
Indicates that the referenced party is the initial or original holder in the specified relationship or arrangement.
-
B.
alsoHeldByFirstHolder
Indicates that something possessed or held by a second holder is (or was) also possessed or held by the first holder.
-
C.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
-
D.
first_holder
Indicates that the subject is the earliest or original holder or possessor of the specified object, title, or right.
-
E.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
- F. None of above. chosen
Provenance (4 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 21, 2026, 1:12 p.m.