Triple
T3788359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Ski Jumping Centre |
E85582
|
entity |
| Predicate | hasAthleteFacilities |
P12416
|
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: [National Ski Jumping Centre, hasAthleteFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAthleteFacilities Context triple: [National Ski Jumping Centre, hasAthleteFacilities, yes]
-
A.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
-
B.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
-
C.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
D.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d4bc3c81909bd56e33d43fa8e4 |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.