Triple
T4668759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarvisio |
E102909
|
entity |
| Predicate | hasSportEvent |
P10279
|
FINISHED |
| Object | Alpine skiing competitions |
—
|
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: Alpine skiing competitions | Statement: [Tarvisio, hasSportEvent, Alpine skiing competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportEvent Context triple: [Tarvisio, hasSportEvent, Alpine skiing competitions]
-
A.
hasSportingEvent
chosen
Indicates that a sporting event is associated with, held at, or organized by a given entity.
-
B.
hasConferenceSport
Indicates that an institution participates in or is associated with a particular sport within a specific athletic conference.
-
C.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
D.
hasSportingContext
Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
-
E.
hasMajorSport
Indicates that an entity is associated with or participates in a primary or most prominent sport.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.