Triple
T3915475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Council |
E88826
|
entity |
| Predicate | mayBeChairedBy |
P48120
|
FINISHED |
| Object | head of 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: head of state | Statement: [Executive Council, mayBeChairedBy, head of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeChairedBy Context triple: [Executive Council, mayBeChairedBy, head of state]
-
A.
canBeChairOf
chosen
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
-
B.
hasCoChairFrom
Indicates that an entity has a co-chair whose affiliation or origin is from a specified source, organization, or group.
-
C.
chairpersonEligibility
Indicates whether an entity meets the required conditions to serve as a chairperson in a given context or organization.
-
D.
coChairpersonOf
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
-
E.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.