Triple
T6107412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shavkat Rakhmonov |
E136149
|
entity |
| Predicate | isUndefeatedIn |
P63159
|
FINISHED |
| Object | professional mixed martial arts |
—
|
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 mixed martial arts | Statement: [Shavkat Rakhmonov, isUndefeatedIn, professional mixed martial arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUndefeatedIn Context triple: [Shavkat Rakhmonov, isUndefeatedIn, professional mixed martial arts]
-
A.
isUndefeated
chosen
Indicates that an entity has not been defeated in any relevant contest, match, or competition.
-
B.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
D.
wasBeaten
Indicates that one entity defeated or physically overpowered another in a contest, conflict, or confrontation.
-
E.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b81fad081909b622cafc6d51249 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.