Triple
T36153113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC featherweight division |
E1045646
|
entity |
| Predicate | allowsGrappling |
P122406
|
FINISHED |
| Object | takedowns |
—
|
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: takedowns | Statement: [UFC featherweight division, allowsGrappling, takedowns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsGrappling Context triple: [UFC featherweight division, allowsGrappling, takedowns]
-
A.
grapplingAllowed
chosen
Indicates that engaging in grappling (close-quarters holds, clinches, or wrestling maneuvers) between the involved parties is permitted.
-
B.
isGrapplingArt
Indicates that the subject is a martial art or combat style primarily focused on grappling techniques such as holds, locks, and throws.
-
C.
usesRopes
Indicates that one entity employs or relies on ropes as tools or components in performing an action or fulfilling a function.
-
D.
cannotBeGraspedAs
Indicates that one entity is not capable of being mentally or conceptually understood in the manner or terms defined by another entity or perspective.
-
E.
hasRope
Indicates that one entity possesses, carries, or is equipped with a rope in relation to another context or entity.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:08 p.m.