Triple
T22318305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolteløkka |
E551707
|
entity |
| Predicate | hasBuildingHeightTypical |
P573
|
FINISHED |
| Object | 3–5 storey buildings |
—
|
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: 3–5 storey buildings | Statement: [Bolteløkka, hasBuildingHeightTypical, 3–5 storey buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingHeightTypical Context triple: [Bolteløkka, hasBuildingHeightTypical, 3–5 storey buildings]
-
A.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
B.
typicalHeight
chosen
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
C.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
D.
roofHeight
Indicates the vertical distance or elevation of a roof relative to a reference level or structure.
-
E.
buildingHeightCharacteristic
Indicates the specific height-related property or measurement that characterizes a building.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157543d688190a151fade71880131 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.