Triple
T2131466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libyan Political Agreement |
E46547
|
entity |
| Predicate | soughtTo |
P34994
|
FINISHED |
| Object | create unified executive authority in Libya |
—
|
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: create unified executive authority in Libya | Statement: [Libyan Political Agreement, soughtTo, create unified executive authority in Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtTo Context triple: [Libyan Political Agreement, soughtTo, create unified executive authority in Libya]
-
A.
soughtTitle
Indicates that an entity actively pursued or attempted to obtain a particular title or position.
-
B.
laterSought
Indicates that one entity attempted to obtain, pursue, or request another entity at a subsequent time relative to some prior reference point.
-
C.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
D.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
-
E.
soughtToMaintain
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb79f21881909ad8d1a09c1f29fd |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb860a51c8190b4ae3bb1cedc0fa0 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:44 p.m.