Triple
T31572504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dempsey–Tunney boxing matches |
E805601
|
entity |
| Predicate | featuredChampionEnteringSeries |
P40092
|
FINISHED |
| Object | Jack Dempsey |
—
|
NE NERFINISHED |
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: Jack Dempsey | Statement: [Dempsey–Tunney boxing matches, featuredChampionEnteringSeries, Jack Dempsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredChampionEnteringSeries Context triple: [Dempsey–Tunney boxing matches, featuredChampionEnteringSeries, Jack Dempsey]
-
A.
featuredChampion
Indicates that an entity is highlighted or designated as a primary or special champion in a given context or event.
-
B.
featuredChallenger
Indicates that an entity is highlighted or designated as a primary or special challenger in a given context or competition.
-
C.
championEnteringBout
chosen
Indicates that an entity who holds a championship title is entering or participating in a competitive bout or match.
-
D.
firstChampion
Indicates that one entity is the earliest or original champion or title-holder in relation to another entity.
-
E.
sawNewChampionCrowned
Indicates that an entity witnessed the moment when a new champion was officially declared or crowned.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: April 30, 2026, 10:20 p.m.