Triple
T35197264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGovern–Fraser reforms |
E1016294
|
entity |
| Predicate | commissionCoChair |
P29942
|
FINISHED |
| Object | Donald M. Fraser |
—
|
NE NERFINISHED |
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: Donald M. Fraser | Statement: [McGovern–Fraser reforms, commissionCoChair, Donald M. Fraser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionCoChair Context triple: [McGovern–Fraser reforms, commissionCoChair, Donald M. Fraser]
-
A.
coChairpersonOf
chosen
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
-
B.
hasCoChair
Indicates that an entity shares the role of chair (leadership or oversight position) jointly with another entity.
-
C.
hasCoChairFrom
Indicates that an entity has a co-chair whose affiliation or origin is from a specified source, organization, or group.
-
D.
chairOfCommission
Indicates that one entity serves as the chairperson or head of a specific commission associated with another entity.
-
E.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.