Triple
T28843669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington College |
E728390
|
entity |
| Predicate | hadGovernance |
P46
|
FINISHED |
| Object | president |
—
|
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: president | Statement: [Burlington College, hadGovernance, president]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadGovernance Context triple: [Burlington College, hadGovernance, president]
-
A.
governance
chosen
Indicates the relationship in which one entity exercises authority, control, or decision-making power over the policies, actions, or direction of another entity or system.
-
B.
hasGovernanceForm
Indicates that an entity is organized or administered according to a particular system or form of governance.
-
C.
governanceIncludes
Indicates that a governance structure or framework encompasses, incorporates, or has authority over the specified component, process, or entity.
-
D.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
E.
selfGovernedBy
Indicates that an entity independently controls and manages itself without external governance.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6597535488190ba3c86bfa33bf14e |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:41 a.m.