Triple
T37045963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Scottish Parliament election |
E916907
|
entity |
| Predicate | scheduledInterval |
P46358
|
FINISHED |
| Object | 5 years |
—
|
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: 5 years | Statement: [2021 Scottish Parliament election, scheduledInterval, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledInterval Context triple: [2021 Scottish Parliament election, scheduledInterval, 5 years]
-
A.
scheduledAfter
Indicates that one event or action is planned to occur later in time than another in a defined schedule or sequence.
-
B.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
C.
schedulePattern
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
D.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
E.
intervalAct
chosen
Indicates an action or relationship that occurs over, or is defined by, a specific time interval between entities.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.