Triple
T8176700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian |
E190952
|
entity |
| Predicate | canHoldPassport |
P81269
|
FINISHED |
| Object | Nigerian passport |
—
|
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: Nigerian passport | Statement: [Nigerian, canHoldPassport, Nigerian passport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHoldPassport Context triple: [Nigerian, canHoldPassport, Nigerian passport]
-
A.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
B.
mayHoldCitizenshipOf
Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
-
C.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
D.
hasCitizenshipRestriction
Indicates that there is a legal or policy-based limitation on who can obtain or hold citizenship in a given context.
-
E.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4aba0dd88190828080d0d89612eb |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:40 p.m.