Triple
T30125265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish devolution referendum, 1979 |
E765677
|
entity |
| Predicate | thresholdMet |
P168826
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Scottish devolution referendum, 1979, thresholdMet, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thresholdMet Context triple: [Scottish devolution referendum, 1979, thresholdMet, no]
-
A.
thresholdFor
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
B.
metropolitanThreshold
Indicates that a place has reached or exceeded the population or density level required to be classified as a metropolitan area.
-
C.
closureThreshold
Indicates the limit or boundary value at which a process, operation, or state is considered complete or closed.
-
D.
baselineLimit
Indicates a threshold or maximum baseline level that something is not expected or allowed to exceed.
-
E.
metThrough
Indicates that two entities became acquainted or connected as a result of an intermediary person, event, platform, or context through which they first met.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67def29e4819089a24fac521054f6 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:14 p.m.