Triple
T15305618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saami Ráđđi |
E365889
|
entity |
| Predicate | representsAcross |
P72867
|
FINISHED |
| Object | traditional Sámi territories |
—
|
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: traditional Sámi territories | Statement: [Saami Ráđđi, representsAcross, traditional Sámi territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsAcross Context triple: [Saami Ráđđi, representsAcross, traditional Sámi territories]
-
A.
centralCrossRepresents
Indicates that a central cross symbol stands for or signifies a particular concept, object, or meaning within a given context.
-
B.
across
Indicates a spatial relationship where one entity is on the opposite side of, or extending from one side to the other side of, another entity or area.
-
C.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
D.
appliesAcross
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
-
E.
representsAs
chosen
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccef14c819099c5ebe962e7f867 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.