Triple
T3763454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gao Region |
E82615
|
entity |
| Predicate | wasFocalPointOf |
P35270
|
FINISHED |
| Object | French-led intervention in Mali |
—
|
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: French-led intervention in Mali | Statement: [Gao Region, wasFocalPointOf, French-led intervention in Mali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFocalPointOf Context triple: [Gao Region, wasFocalPointOf, French-led intervention in Mali]
-
A.
hasBeenSubjectOf
chosen
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
-
B.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
C.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
-
D.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfbecf8819099d80af480cbe2d2 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.