Triple
T15448174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brumunddal |
E370077
|
entity |
| Predicate | MjøstårnetInstanceOf |
P118823
|
FINISHED |
| Object | tall timber building |
—
|
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: tall timber building | Statement: [Brumunddal, MjøstårnetInstanceOf, tall timber building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MjøstårnetInstanceOf Context triple: [Brumunddal, MjøstårnetInstanceOf, tall timber building]
-
A.
tallestBuildingIn
Indicates that one entity is the tallest building located within the area or region specified by the other entity.
-
B.
tower
Indicates that one entity is a tall, prominent structure rising above its surroundings, often used for observation, support, or communication.
-
C.
towerName
Indicates the specific name assigned to a tower in the relationship.
-
D.
partOfSkylineOf
Indicates that one entity is a visible component or feature contributing to the overall skyline profile of another entity, typically a city or urban area.
-
E.
oneOfTallestStructuresIn
Indicates that an entity is among the tallest structures located within a specified place or region.
- F. None of above. chosen
Provenance (4 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef767b4819099f2c0919a158321 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.