Triple
T1057552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regjeringskvartalet |
E22829
|
entity |
| Predicate | hasMapFeature |
P182
|
FINISHED |
| Object | urban government district |
—
|
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: urban government district | Statement: [Regjeringskvartalet, hasMapFeature, urban government district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapFeature Context triple: [Regjeringskvartalet, hasMapFeature, urban government district]
-
A.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
B.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
C.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
isOnSystemMap
Indicates that an entity is currently displayed or represented on a particular system map.
-
E.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4ba6e35ac8190802341c31bda0e3b |
completed | March 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69a4b7340a048190807363f19d17a58f |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.