Triple
T35886030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 99 |
E1037644
|
entity |
| Predicate | firstUFCEventInCountry |
P8095
|
FINISHED |
| Object | Germany |
E1728
|
NE 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: Germany | Statement: [UFC 99, firstUFCEventInCountry, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUFCEventInCountry Context triple: [UFC 99, firstUFCEventInCountry, Germany]
-
A.
madeUFCDebutAtEvent
Indicates that an individual’s first fight or appearance in the UFC occurred at a specified event.
-
B.
foundedUFCEventNumber
Indicates that an entity established or created the specific UFC event identified by its event number.
-
C.
firstUFCEventWithHeavyweights
Indicates the event that was the earliest UFC competition to feature heavyweight fighters.
-
D.
countryOfFirstEvent
chosen
Indicates the country in which the first event in a sequence or series took place.
-
E.
UFCDebutResult
Indicates the outcome of a fighter’s first bout in the UFC, specifying how that debut fight concluded.
- F. None of above.
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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ae1268cc8190bd995b474aa5f023 |
completed | June 22, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.