Triple
T31954156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagos incident |
E815858
|
entity |
| Predicate | chronologicalPrecededBy |
P33474
|
FINISHED |
| Object | Sokovia incident |
—
|
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: Sokovia incident | Statement: [Lagos incident, chronologicalPrecededBy, Sokovia incident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPrecededBy Context triple: [Lagos incident, chronologicalPrecededBy, Sokovia incident]
-
A.
chronologyPrecedes
chosen
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
B.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
C.
precedesInUniverse
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
- 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_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 12:08 a.m.