Triple
T24063258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Open |
E596012
|
entity |
| Predicate | coSanctioningStartYear |
P154710
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Scottish Open, coSanctioningStartYear, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coSanctioningStartYear Context triple: [Scottish Open, coSanctioningStartYear, 2022]
-
A.
coSanctionedSince
Indicates that two or more entities have jointly imposed or been subject to a sanction starting from a specified point in time and continuing thereafter.
-
B.
sanctionYear
Indicates the year in which a sanction was imposed, enacted, or came into effect.
-
C.
coSanctionedBy
Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
-
D.
coSanctionedWith
Indicates that an entity is subject to sanctions together with another entity, typically as part of the same sanctioning action or regime.
-
E.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5825548190b94cb6e708617a7d |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:39 p.m.