Triple
T22917905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos Condit |
E568780
|
entity |
| Predicate | hasWonBonusAward |
P128987
|
FINISHED |
| Object | Fight of the Night |
—
|
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: Fight of the Night | Statement: [Carlos Condit, hasWonBonusAward, Fight of the Night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWonBonusAward Context triple: [Carlos Condit, hasWonBonusAward, Fight of the Night]
-
A.
hasWonBonus
chosen
Indicates that an entity has received or been awarded a bonus, typically as a result of meeting certain conditions or achieving specific performance.
-
B.
hasGrandPrize
Indicates that an entity possesses, is awarded, or is associated with a grand prize in a given context.
-
C.
hasRewardStatus
Indicates that an entity possesses a particular reward-related condition, level, or eligibility status within a reward system.
-
D.
hasBonusMaterial
Indicates that an item includes additional supplementary content beyond its main or primary material.
-
E.
hasAdditionalPrizes
Indicates that an entity offers or is associated with extra prizes beyond the primary or standard ones.
- 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.