Triple
T3701510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harstad |
E78588
|
entity |
| Predicate | populationRankInNorthernNorway |
P25930
|
FINISHED |
| Object | one of the largest towns |
—
|
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: one of the largest towns | Statement: [Harstad, populationRankInNorthernNorway, one of the largest towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInNorthernNorway Context triple: [Harstad, populationRankInNorthernNorway, one of the largest towns]
-
A.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
B.
distanceFromOslo
Indicates the spatial distance between a given entity’s location and the city of Oslo.
-
C.
countryRankContext
Indicates the relative position or ranking of a country within a specified contextual framework (such as economic, political, or performance-based criteria).
-
D.
hasPopulationRankInRegion
chosen
Indicates that an entity has a specific population-based rank or position within a defined geographic region.
-
E.
nationalRank
Indicates the position or standing of an entity within a ranking system at the national level.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc547c1848190a1ece46c59b7c43d |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adb84eeca48190bb4de637e9f0e27a |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.