Triple
T2021067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powder |
E44105
|
entity |
| Predicate | associatedWithSportType |
P5085
|
FINISHED |
| Object | winter sports |
—
|
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: winter sports | Statement: [Powder, associatedWithSportType, winter sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSportType Context triple: [Powder, associatedWithSportType, winter sports]
-
A.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
B.
relationshipTypeWithSport
Indicates the specific type or nature of the relationship an entity has with a particular sport (e.g., participation, affiliation, or role).
-
C.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
D.
appliesToSports
chosen
Indicates that something is relevant, appropriate, or specifically intended for use in the context of sports.
-
E.
representsInSport
Indicates that one entity serves as an official representative of another entity within the context of a particular sport or sporting domain.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.