Triple
T31954147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagos incident |
E815858
|
entity |
| Predicate | organizationOverseeingResponse |
P30657
|
FINISHED |
| Object | United Nations |
—
|
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: United Nations | Statement: [Lagos incident, organizationOverseeingResponse, United Nations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationOverseeingResponse Context triple: [Lagos incident, organizationOverseeingResponse, United Nations]
-
A.
organOrganization
Indicates that an organ is structurally or functionally part of, or associated with, a specific organization or organizational system.
-
B.
endedOrganization
Indicates that an organization has ceased to exist or operate, marking the termination of its existence or activities.
-
C.
organizationTypeGoverned
Indicates that one entity governs or has authoritative control over a specific type or category of organization.
-
D.
organizationLed
chosen
Indicates that one organization provides leadership, direction, or governance over another organization or collective effort.
-
E.
organizationTypeLed
Indicates that an entity holds a leadership role over an organization of a specified type.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 12:08 a.m.