Triple
T35673103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock Lesnar vs. Randy Couture |
E1030777
|
entity |
| Predicate | fighter1TeamStyle |
P165038
|
FINISHED |
| Object | wrestling-based heavyweight |
—
|
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: wrestling-based heavyweight | Statement: [Brock Lesnar vs. Randy Couture, fighter1TeamStyle, wrestling-based heavyweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighter1TeamStyle Context triple: [Brock Lesnar vs. Randy Couture, fighter1TeamStyle, wrestling-based heavyweight]
-
A.
fighter1Style
Indicates the fighting style or combat approach used by the first fighter in a matchup or comparison.
-
B.
fighter1StyleDescription
chosen
Indicates the descriptive characterization of the fighting style used by the first fighter in a matchup or comparison.
-
C.
fighter2Style
Indicates the fighting style or combat approach used by the second fighter in a matchup or interaction.
-
D.
teamStyle
Indicates the characteristic way a team typically operates, collaborates, and approaches its work or objectives.
-
E.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.