Triple
T24475128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PASO |
E617211
|
entity |
| Predicate | hasSportScope |
P15165
|
FINISHED |
| Object | multi-sport |
—
|
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: multi-sport | Statement: [PASO, hasSportScope, multi-sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportScope Context triple: [PASO, hasSportScope, multi-sport]
-
A.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
B.
hasSportsFunction
Indicates that an entity serves a role, purpose, or function related to sports activities or sports-related operations.
-
C.
hasSportingContext
Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
-
D.
hasSportsBody
Indicates that an entity possesses a body or physique that is characteristic of someone who regularly engages in sports or athletic activities.
-
E.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29947084081908895573a4a4e4822 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.