Triple
T24745000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Trustees (Drake University) |
E618669
|
entity |
| Predicate | typicalOfficerRole |
P18942
|
FINISHED |
| Object | vice chair |
—
|
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: vice chair | Statement: [Board of Trustees (Drake University), typicalOfficerRole, vice chair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOfficerRole Context triple: [Board of Trustees (Drake University), typicalOfficerRole, vice chair]
-
A.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
C.
officersServeAs
Indicates that certain individuals hold and perform the role or duties of officers within a particular organization or context.
-
D.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
E.
tacticalOfficer
Indicates that an entity serves in the role or capacity of a tactical officer in relation to another entity or organization.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 4:21 a.m.