Triple
T1111783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of Nigeria |
E11010
|
entity |
| Predicate | requiresOath |
P16811
|
FINISHED |
| Object | Oath of Allegiance |
—
|
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: Oath of Allegiance | Statement: [President of Nigeria, requiresOath, Oath of Allegiance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresOath Context triple: [President of Nigeria, requiresOath, Oath of Allegiance]
-
A.
requiredRiderOath
Indicates that an individual is obligated to take or uphold a specific rider’s oath as a condition for participation or status.
-
B.
hasOathTo
chosen
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
C.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
D.
requiresProofOf
Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
-
E.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.