Triple
T25996719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emile Griffith vs Benny Paret III |
E646504
|
entity |
| Predicate | tookPlaceInRingSport |
P104224
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Emile Griffith vs Benny Paret III, tookPlaceInRingSport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceInRingSport Context triple: [Emile Griffith vs Benny Paret III, tookPlaceInRingSport, true]
-
A.
tookPlaceInMatch
chosen
Indicates that an event or action occurred during a specific match.
-
B.
requiresRingOfficials
Indicates that the event or activity cannot proceed or be valid unless designated ring officials are present or assigned.
-
C.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
D.
competitionDepicted
Indicates that a competitive event or rivalry between entities is shown or represented in some medium or context.
-
E.
wrestlerRingNameContext
Indicates that a particular ring name is used by a wrestler within a specific contextual setting, such as a promotion, time period, or storyline.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6056f481c81909fd23b04483b76a0 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:58 a.m.