Triple
T28300396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union pour un Mouvement Populaire |
E713691
|
entity |
| Predicate | backedLeader |
P33755
|
FINISHED |
| Object | Nicolas Sarkozy |
—
|
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: Nicolas Sarkozy | Statement: [Union pour un Mouvement Populaire, backedLeader, Nicolas Sarkozy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backedLeader Context triple: [Union pour un Mouvement Populaire, backedLeader, Nicolas Sarkozy]
-
A.
supportedLeader
chosen
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
B.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
C.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
D.
servedUnderLeader
Indicates that one entity held a position or role subordinate to, and operating under the authority or command of, another specified leader.
-
E.
executedLeader
Indicates that a leader was put to death, typically as a result of a formal or authoritative execution.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644b1f4448190896e0b0d5cbc6872 |
completed | May 2, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:34 p.m.