Triple
T22240478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area Health Boards (Scotland) |
E549704
|
entity |
| Predicate | hadChair |
P37547
|
FINISHED |
| Object | health board chairperson |
—
|
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 chairperson | Statement: [Area Health Boards (Scotland), hadChair, health board chairperson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChair Context triple: [Area Health Boards (Scotland), hadChair, health board chairperson]
-
A.
chairIn
Indicates that one entity is a chair located within the spatial bounds or interior of another entity.
-
B.
canChair
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
C.
hasChairs
Indicates that one entity possesses, contains, or is equipped with one or more chairs.
-
D.
favoriteChair
Indicates that one entity is the preferred or most liked chair of another entity.
-
E.
boardChair
chosen
Indicates that one entity serves as the chairperson (leader) of the board of directors 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.