Triple
T22188410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Military Government of Nigeria |
E548353
|
entity |
| Predicate | firstCoupDate |
P146775
|
FINISHED |
| Object | 15 January 1966 |
—
|
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: 15 January 1966 | Statement: [Federal Military Government of Nigeria, firstCoupDate, 15 January 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCoupDate Context triple: [Federal Military Government of Nigeria, firstCoupDate, 15 January 1966]
-
A.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
B.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
C.
firstPowerDate
Indicates the date on which an entity first began to generate or use power.
-
D.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
E.
firstInternationalDate
Indicates that one entity is the earliest (chronologically first) international date associated with 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aab3d2c81908a3b5a5c127c4aac |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.