Triple
T14407551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronda Rousey |
E357237
|
entity |
| Predicate | wrestlingFinisher |
P114135
|
FINISHED |
| Object | armbar |
—
|
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: armbar | Statement: [Ronda Rousey, wrestlingFinisher, armbar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestlingFinisher Context triple: [Ronda Rousey, wrestlingFinisher, armbar]
-
A.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
-
B.
notableFatality
Indicates that an entity is a significant or widely recognized example of a death associated with another entity or event.
-
C.
typeOfWrestling
Indicates the specific style or category of wrestling that characterizes a given wrestling activity or event.
-
D.
featuredMatchStipulation
Indicates that a particular rule, condition, or special stipulation is prominently associated with a highlighted or main match.
-
E.
positionInWrestling
Indicates the specific physical hold, stance, or arrangement of wrestlers relative to each other during a wrestling exchange or sequence.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90c7a068819081b4b516983a1412 |
completed | April 14, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:17 a.m.