Triple
T23165598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 2 |
E578703
|
entity |
| Predicate | notableFighter |
P101800
|
FINISHED |
| Object | Royce Gracie |
—
|
NE NERFINISHED |
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: Royce Gracie | Statement: [UFC 2, notableFighter, Royce Gracie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFighter Context triple: [UFC 2, notableFighter, Royce Gracie]
-
A.
featuredFighter
chosen
Indicates that a particular fighter is highlighted or prominently showcased in a given context or event.
-
B.
notableFormerChampion
Indicates that an entity was once a champion of something and is recognized as particularly distinguished or prominent in that former champion role.
-
C.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
D.
formerBoxer
Indicates that a person previously worked or competed as a boxer but no longer does so.
-
E.
hasNotableBoxer
Indicates that an entity is associated with or characterized by a boxer who is considered notable or distinguished.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.