Triple
T27764341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EHC Arosa |
E701557
|
entity |
| Predicate | historicallyTopTier |
P84360
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [EHC Arosa, historicallyTopTier, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyTopTier Context triple: [EHC Arosa, historicallyTopTier, yes]
-
A.
historicalTopCompetition
chosen
Indicates that an entity has participated in or been associated with the highest-level or most prestigious competition within a historical context.
-
B.
historicallyDominantIn
Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
-
C.
historicalLevel
Indicates the degree or extent to which something is related to, situated in, or characterized by a particular historical period or context.
-
D.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
-
E.
historicalStrength
Indicates the relative power, influence, or effectiveness an entity possessed during a specified past period.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 27, 2026, 4:29 p.m.