Triple
T36565559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown entity |
E901964
|
entity |
| Predicate | governedByStructure |
P46501
|
FINISHED |
| Object | board or governing body |
—
|
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: board or governing body | Statement: [Crown entity, governedByStructure, board or governing body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByStructure Context triple: [Crown entity, governedByStructure, board or governing body]
-
A.
governedThrough
chosen
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
-
B.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
C.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
D.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
E.
governedByAct
Indicates that something is regulated, controlled, or legally defined by a specific act or piece of legislation.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: May 3, 2026, 4:11 p.m.