Triple
T35658781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sääʹmteʹǧǧ |
E1030368
|
entity |
| Predicate | hasRightToBeConsultedOn |
P192809
|
FINISHED |
| Object | legislation affecting Sámi in Finland |
—
|
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: legislation affecting Sámi in Finland | Statement: [Sääʹmteʹǧǧ, hasRightToBeConsultedOn, legislation affecting Sámi in Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightToBeConsultedOn Context triple: [Sääʹmteʹǧǧ, hasRightToBeConsultedOn, legislation affecting Sámi in Finland]
-
A.
hasDataSubjectRight
Indicates that a data subject holds a specific legal right or entitlement in relation to the processing of their personal data.
-
B.
hasGivenConsentFor
Indicates that one entity has granted permission or approval for a specific action, process, or use involving another entity or resource.
-
C.
hasCounsel
Indicates that one entity serves as a legal advisor or representative (counsel) for another entity.
-
D.
consulted
Indicates that one entity sought advice, information, or guidance from another entity.
-
E.
mayConsultWith
Indicates that one entity is permitted or allowed to seek advice, guidance, or professional input from another entity.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: May 3, 2026, 4:05 p.m.