Triple
T24361651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val di Fiemme |
E614075
|
entity |
| Predicate | sportFacility |
P2500
|
FINISHED |
| Object | Lago di Tesero Cross Country Stadium |
—
|
NE NERFINISHED |
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: Lago di Tesero Cross Country Stadium | Statement: [Val di Fiemme, sportFacility, Lago di Tesero Cross Country Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportFacility Context triple: [Val di Fiemme, sportFacility, Lago di Tesero Cross Country Stadium]
-
A.
sportsFacility
chosen
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
-
B.
sportsInfrastructureDevelopedFor
Indicates that sports-related facilities or structures have been created, improved, or established for the benefit or use of a particular entity.
-
C.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
D.
gameVenue
Indicates the location or facility where a game or match is held.
-
E.
coordinatesSportingInfrastructureWith
Indicates that one entity collaborates or organizes with another to plan, align, or manage sporting facilities, resources, or related infrastructure.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29384a2f88190885eb141c5c44a2d |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.