Triple
T8908733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish devolution referendum, 1997 |
E212127
|
entity |
| Predicate | resultQuestion2 |
P86316
|
FINISHED |
| Object | Yes majority |
—
|
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 majority | Statement: [Scottish devolution referendum, 1997, resultQuestion2, Yes majority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultQuestion2 Context triple: [Scottish devolution referendum, 1997, resultQuestion2, Yes majority]
-
A.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
-
B.
questionFormulation
Indicates that one entity formulates, poses, or expresses a question directed toward another entity or context.
-
C.
questionText
Indicates the textual content of a question as it is posed or displayed.
-
D.
relatedQuestion
Indicates that one question is connected to another by topic, context, or relevance, suggesting they are meaningfully associated.
-
E.
guidingQuestionOf
Indicates that one item serves as a guiding or central question that frames, directs, or structures another item (such as a discussion, activity, or work).
- F. None of above. chosen
Provenance (4 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65207bbc8190be181555b9564797 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc604965c48190bbb6db0ae8108e67 |
completed | April 1, 2026, 12:01 a.m. |
Created at: March 30, 2026, 6:55 p.m.