Triple
T13797825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIS Ski Flying World Championships |
E331560
|
entity |
| Predicate | hillSizeRequirement |
P15211
|
FINISHED |
| Object | HS185 or larger |
—
|
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: HS185 or larger | Statement: [FIS Ski Flying World Championships, hillSizeRequirement, HS185 or larger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hillSizeRequirement Context triple: [FIS Ski Flying World Championships, hillSizeRequirement, HS185 or larger]
-
A.
hasHillSize
chosen
Indicates that something possesses or is characterized by a particular hill size.
-
B.
hillType
Indicates the specific classification or category of a hill based on its form, characteristics, or context.
-
C.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
D.
densityRequirement
Indicates that there is a specified minimum or target density that must be met or maintained in the relationship between the related entities.
-
E.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025be1f08190aac525d72d7dc0c3 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.