Triple
T20999358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levanger |
E517242
|
entity |
| Predicate | grantedTownStatusInNorway |
P3431
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Levanger, grantedTownStatusInNorway, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedTownStatusInNorway Context triple: [Levanger, grantedTownStatusInNorway, 1997]
-
A.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
-
B.
cityStatusGrantedBy
Indicates that one entity (such as a person, authority, or institution) formally granted or conferred city status upon another entity (typically a settlement or locality).
-
C.
cityStatusGrantedIn
Indicates the event or point in time at which an entity was officially granted city status in a particular place or jurisdiction.
-
D.
grantedTownRights
chosen
Indicates that an authority formally conferred municipal or town privileges and legal status upon a settlement.
-
E.
grantedCityStatusFor
Indicates that an authority has officially conferred city status upon an entity for a specified reason or basis.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc2395108190871e173354e4ef6f |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:51 p.m.