Triple
T22917652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristar Gym |
E568775
|
entity |
| Predicate | associatedWithFighterRole |
P68183
|
FINISHED |
| Object | UFC champion training |
—
|
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: UFC champion training | Statement: [Tristar Gym, associatedWithFighterRole, UFC champion training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFighterRole Context triple: [Tristar Gym, associatedWithFighterRole, UFC champion training]
-
A.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
-
B.
roleInUFC
chosen
Indicates the specific capacity or position an entity holds within the context of the Ultimate Fighting Championship (UFC), such as fighter, referee, coach, or official.
-
C.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
D.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
E.
featuredFighter
Indicates that a particular fighter is highlighted or prominently showcased in a given context or event.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807b254c8190bb84596dcacaa35e |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.