Triple
T24566173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British heavyweight title |
E607792
|
entity |
| Predicate | locationOfBouts |
P21366
|
FINISHED |
| Object | various venues in the United Kingdom |
—
|
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: various venues in the United Kingdom | Statement: [British heavyweight title, locationOfBouts, various venues in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfBouts Context triple: [British heavyweight title, locationOfBouts, various venues in the United Kingdom]
-
A.
fightsAtLocation
Indicates that a fighting interaction between entities occurs at a specified location.
-
B.
locationOfCompetition
chosen
Indicates the place or venue where a competition or contest takes or took place.
-
C.
playsInArenaLocatedIn
Indicates that an entity performs or participates in events within an arena that is geographically located in a specified place.
-
D.
arenaLocation
Indicates that an arena is located at or within a specified place or geographic location.
-
E.
locationOfSport
Indicates the place where a particular sport is played, practiced, or held.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92082a881908896dcdda85559b9 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.