Triple
T7584045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiruna |
E179561
|
entity |
| Predicate | hasRelocationProject |
P14971
|
FINISHED |
| Object | Kiruna urban transformation |
—
|
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: Kiruna urban transformation | Statement: [Kiruna, hasRelocationProject, Kiruna urban transformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelocationProject Context triple: [Kiruna, hasRelocationProject, Kiruna urban transformation]
-
A.
relocationProject
Indicates a project or organized effort to move an entity from one location to another.
-
B.
hasRelocation
Indicates that one entity is moved, transferred, or reassigned from one location or context to another.
-
C.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
D.
hasProject
chosen
Indicates that an entity is associated with or responsible for a particular project.
-
E.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f993cd0c8190864f801074625a32 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.