Triple
T13481097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Mercer |
E318371
|
entity |
| Predicate | hasCompetitionRecord |
P72801
|
FINISHED |
| Object | world-level heavyweight bouts |
—
|
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: world-level heavyweight bouts | Statement: [Ray Mercer, hasCompetitionRecord, world-level heavyweight bouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionRecord Context triple: [Ray Mercer, hasCompetitionRecord, world-level heavyweight bouts]
-
A.
hasCompetitionHistory
chosen
Indicates that an entity has a recorded history of participation in competitions or competitive events.
-
B.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
C.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
-
D.
hasWonCompetition
Indicates that an entity has achieved victory in a competition or contest against others.
-
E.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf36c6b08190ba99400600e0b662 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.