Triple
T22240479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area Health Boards (Scotland) |
E549704
|
entity |
| Predicate | hadChiefExecutive |
P77600
|
FINISHED |
| Object | health board chief executive |
—
|
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: health board chief executive | Statement: [Area Health Boards (Scotland), hadChiefExecutive, health board chief executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChiefExecutive Context triple: [Area Health Boards (Scotland), hadChiefExecutive, health board chief executive]
-
A.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
-
B.
hadPrincipalLeader
chosen
Indicates that an entity was led or headed by a primary or chief leader.
-
C.
hasPresident
Indicates that an entity holds the position or role of president for another entity.
-
D.
headOfRepublic
Indicates the relationship in which a person holds the highest office and serves as the chief of state of a republic.
-
E.
headOfGovernment
Indicates that one entity serves as the chief executive authority or leader of the government of 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:38 p.m.