Triple
T19934266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norrtälje |
E479132
|
entity |
| Predicate | hasHistoricTownStatus |
P51441
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Norrtälje, hasHistoricTownStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricTownStatus Context triple: [Norrtälje, hasHistoricTownStatus, true]
-
A.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
hasHistoricCenterStatus
chosen
Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
-
C.
hasMarketTownHistory
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
D.
governsHistoricTown
Indicates that one entity exercises official governing authority over a town that is recognized as historically significant.
-
E.
hasCastleTownHistory
Indicates that an entity has a historical association with a castle town, such as originating from, being located in, or significantly shaped by one.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a161a6c819084165ea528ec2f64 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.