Triple
T22850555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yubi Lakpi |
E566343
|
entity |
| Predicate | isNonOlympicSport |
P149945
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yubi Lakpi, isNonOlympicSport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonOlympicSport Context triple: [Yubi Lakpi, isNonOlympicSport, true]
-
A.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
-
B.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
isContactSport
Indicates that the activity involves significant physical contact between participants as an inherent and expected part of play.
-
D.
isInSportSystemOf
Indicates that one entity belongs to, is organized within, or operates under the structure of a particular sport system or sports organizational framework of another entity.
-
E.
OlympicStatus
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:36 p.m.