Triple
T1948893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMC Chairman |
E42115
|
entity |
| Predicate | typicalIncumbentRole |
P18942
|
FINISHED |
| Object | paramount leader of the state |
—
|
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: paramount leader of the state | Statement: [CMC Chairman, typicalIncumbentRole, paramount leader of the state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIncumbentRole Context triple: [CMC Chairman, typicalIncumbentRole, paramount leader of the state]
-
A.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
C.
incumbent
Indicates that an entity currently holds a particular position, office, or role at the present time.
-
D.
electoralRole
Indicates the specific function, position, or capacity an entity holds within an electoral process or system.
-
E.
traditionallyHoldsOffice
Indicates that an entity customarily or historically occupies a particular office or position as part of an established tradition.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3315df481908f60cd87453fbc03 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.