Triple
T23135783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rickson Gracie |
E577315
|
entity |
| Predicate | mmaRecord |
P151050
|
FINISHED |
| Object | professional MMA record commonly cited as 11–0 |
—
|
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 MMA record commonly cited as 11–0 | Statement: [Rickson Gracie, mmaRecord, professional MMA record commonly cited as 11–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mmaRecord Context triple: [Rickson Gracie, mmaRecord, professional MMA record commonly cited as 11–0]
-
A.
mate
Indicates that two entities engage in or are involved in a reproductive pairing or breeding relationship.
-
B.
competitiveRecord
Indicates the win–loss (and possibly tie) outcomes between entities that have competed against each other.
-
C.
professionalRecordDraws
Indicates the number of times a professional competitor’s official matches have ended in a draw.
-
D.
numberOfOpponentsBeaten
Indicates the count of distinct opponents that an entity has successfully defeated.
-
E.
game3Record
Indicates the recorded outcome or performance statistics of a participant in their third game or match within a series or season.
- F. None of above. chosen
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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8b694c8190b9ead00ea0576d90 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4 p.m.