Triple
T528109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikingskipet |
E10967
|
entity |
| Predicate | climateControl |
P2900
|
FINISHED |
| Object | indoor climate-controlled arena |
—
|
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: indoor climate-controlled arena | Statement: [Vikingskipet, climateControl, indoor climate-controlled arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateControl Context triple: [Vikingskipet, climateControl, indoor climate-controlled arena]
-
A.
temperatureControlMethod
Indicates the method or mechanism used to regulate or maintain a desired temperature.
-
B.
climateControlledCabins
Indicates that the subject provides or features cabins whose internal environment (such as temperature and humidity) is actively regulated for comfort or preservation.
-
C.
environmentalCondition
chosen
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
D.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
E.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d2851c81908129f7da932ab7b3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.