Triple
T16262287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stipe Miocic |
E394782
|
entity |
| Predicate | amateurSport |
P17808
|
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: [Stipe Miocic, amateurSport, wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amateurSport Context triple: [Stipe Miocic, amateurSport, wrestling]
-
A.
traditionalSport
Indicates that an entity is a sport practiced within a culture or community that has been passed down over generations and is recognized as part of traditional or heritage activities.
-
B.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
-
C.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
-
D.
secondarySport
chosen
Indicates that an entity participates in or is associated with a sport that is not their primary or main sport.
-
E.
originalSport
Indicates that one sport is the initial or primary sport associated with an entity, often before any change, adaptation, or transition to another 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c5583c8190901e892238cf8dbd |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.