Triple
T15484175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentière Glacier |
E376999
|
entity |
| Predicate | sportsImportance |
P67859
|
FINISHED |
| Object | classic ski mountaineering area |
—
|
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: classic ski mountaineering area | Statement: [Argentière Glacier, sportsImportance, classic ski mountaineering area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsImportance Context triple: [Argentière Glacier, sportsImportance, classic ski mountaineering area]
-
A.
importanceWithinSport
chosen
Indicates the degree to which something is regarded as significant or influential within a particular sport.
-
B.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
C.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
D.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
-
E.
sport
Indicates that an entity participates in, is associated with, or is characterized by a particular athletic activity or game.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8e6ff08190b130b3a38f4190e7 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:45 a.m.