Triple
T31521742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Burr |
E804223
|
entity |
| Predicate | chairmanshipStart |
P114492
|
FINISHED |
| Object | 2015-01-06 |
—
|
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: 2015-01-06 | Statement: [Richard Burr, chairmanshipStart, 2015-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chairmanshipStart Context triple: [Richard Burr, chairmanshipStart, 2015-01-06]
-
A.
chairpersonStart
chosen
Indicates the time or event at which a person begins serving as the chairperson of an organization or group.
-
B.
chairmanshipRotates
Indicates that the role of chairperson is periodically transferred from one individual or entity to another according to a set rotation.
-
C.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
D.
chairpersonUsuallyFrom
Indicates that the person serving as chairperson typically originates from or is selected from the specified group, organization, or category.
-
E.
chairingSystem
Indicates that an entity is responsible for leading, overseeing, or presiding over a particular system or organized structure.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:56 p.m.