Triple
T14486335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijani government |
E359236
|
entity |
| Predicate | hasSecondLeaderTitle |
P31581
|
FINISHED |
| Object | Prime Minister |
—
|
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: Prime Minister | Statement: [Azerbaijani government, hasSecondLeaderTitle, Prime Minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondLeaderTitle Context triple: [Azerbaijani government, hasSecondLeaderTitle, Prime Minister]
-
A.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
B.
hasSecondGenerationLeader
Indicates that an entity is led or governed by a leader belonging to its second generation of leadership.
-
C.
hasCollectiveLeaderTitle
Indicates that a collective entity (such as a group, organization, or body) holds or is associated with a specific leadership title.
-
D.
secondLeader
chosen
Indicates that an entity serves as the second-ranking leader or deputy leader in relation to another entity.
-
E.
hasFormerLeader
Indicates that an entity previously held the role of leader of another entity but no longer does.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.