Triple
T35139010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongo McMichael |
E1014651
|
entity |
| Predicate | individualSport |
P179726
|
FINISHED |
| Object | professional 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: professional wrestling | Statement: [Mongo McMichael, individualSport, professional wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: individualSport Context triple: [Mongo McMichael, individualSport, professional wrestling]
-
A.
sportsIdentity
Indicates that an entity’s identity, role, or affiliation is defined in the context of sports (e.g., as an athlete, team, or sports-related organization).
-
B.
inSportDiscipline
chosen
Indicates that an entity participates, competes, or is involved in a specific sport discipline or event.
-
C.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
D.
parentSport
Indicates that one sport is the broader or more general category from which another sport is derived or classified.
-
E.
countrySport
Indicates that a particular sport is commonly played in, associated with, or represents a country.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ca7c87c81908f1648733f2ea3db |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.