Triple
T30861880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Sidra incident 1986 |
E786080
|
entity |
| Predicate | LibyanLeader |
P170797
|
FINISHED |
| Object | Muammar Gaddafi |
—
|
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: Muammar Gaddafi | Statement: [Gulf of Sidra incident 1986, LibyanLeader, Muammar Gaddafi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LibyanLeader Context triple: [Gulf of Sidra incident 1986, LibyanLeader, Muammar Gaddafi]
-
A.
LibyanLeaderAtTime
chosen
Indicates that a given person holds the position of leader of Libya during a specified time period.
-
B.
recognizedAsLibyaRepresentativeBy
Indicates that an entity is officially acknowledged or accepted as the legitimate representative of Libya by another specified party.
-
C.
coupLeader
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
D.
belligerentLeader
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
-
E.
ISILCommander
Indicates that one entity serves as a commander within the organization ISIL in relation to another entity or context.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:47 p.m.