Triple
T29799118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greatest |
E756640
|
entity |
| Predicate | bearerSignatureFight |
P159052
|
FINISHED |
| Object | Fight of the Century vs. Joe Frazier |
—
|
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: Fight of the Century vs. Joe Frazier | Statement: [The Greatest, bearerSignatureFight, Fight of the Century vs. Joe Frazier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerSignatureFight Context triple: [The Greatest, bearerSignatureFight, Fight of the Century vs. Joe Frazier]
-
A.
bearerNotableFight
chosen
Indicates that the bearer has participated in a specific fight or combat event that is considered notable or significant.
-
B.
hasFight
Indicates that one entity engages in a physical or verbal conflict with another entity.
-
C.
bearerRivalOf
Indicates that the bearer is in a state of rivalry or competitive opposition with the related entity.
-
D.
fightType
Indicates the specific category or style of fight associated with an event or interaction between entities.
-
E.
peakFighting
Indicates that an entity is engaging in combat or conflict at the highest or most intense level of its fighting capability.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 5:17 p.m.