Triple
T29644616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDSB |
E755962
|
entity |
| Predicate | hasBoardOfTrustees |
P176829
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DDSB, hasBoardOfTrustees, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoardOfTrustees Context triple: [DDSB, hasBoardOfTrustees, yes]
-
A.
isBoardOf
Indicates that an entity serves as the governing board or board member for another entity (such as an organization, company, or institution).
-
B.
trusteeshipSystem
Indicates a relationship in which one entity holds and manages authority or responsibility over another entity or territory on its behalf, typically under an established oversight or governance framework.
-
C.
trustBoardEstablished
chosen
Indicates that a formal trust board has been created and put into operation to oversee or manage certain responsibilities or assets.
-
D.
boardOf
Indicates that one entity serves as the governing board or board member(s) responsible for overseeing another entity.
-
E.
hasBoardOrCommission
Indicates that an entity is associated with, oversees, or is served by a specific board or commission.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 6:49 p.m.