Triple
T35858981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sports Pavilion |
E1036587
|
entity |
| Predicate | hasAlternativeSport |
P195613
|
FINISHED |
| Object | wrestling |
—
|
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: wrestling | Statement: [Sports Pavilion, hasAlternativeSport, wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeSport Context triple: [Sports Pavilion, hasAlternativeSport, wrestling]
-
A.
alsoUsedForSport
Indicates that something primarily associated with one purpose is additionally used for sporting activities or athletic purposes.
-
B.
sportCreatedAsAlternativeTo
Indicates that one sport was developed specifically to serve as a substitute or alternative to another sport.
-
C.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
D.
secondarySport
Indicates that an entity participates in or is associated with a sport that is not their primary or main sport.
-
E.
hasSportsOffered
Indicates that an entity provides or makes available certain sports as options or activities.
- F. None of above. chosen
Provenance (4 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69fddac42c4081908568649058e86458 |
completed | May 8, 2026, 12:44 p.m. |
Created at: May 3, 2026, 4:06 p.m.