Triple
T7117469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terence Crawford |
E165854
|
entity |
| Predicate | isWorldChampionIn |
P21542
|
FINISHED |
| Object | multiple weight divisions |
—
|
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: multiple weight divisions | Statement: [Terence Crawford, isWorldChampionIn, multiple weight divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWorldChampionIn Context triple: [Terence Crawford, isWorldChampionIn, multiple weight divisions]
-
A.
hasWorldChampionship
Indicates that an entity possesses, has won, or holds a world championship title or status.
-
B.
worldChampionIn
chosen
Indicates that an entity holds or has held the title of world champion in a specified field, discipline, or competition.
-
C.
featuredWorldChampion
Indicates that an entity has been highlighted or showcased specifically in its capacity as a world champion.
-
D.
stateOfChampion
Indicates the relationship in which an entity holds the status or title of being a champion in a particular context or competition.
-
E.
wonChampionshipAsPlayerWith
Indicates that one entity won a championship while playing on a team or alongside the other entity.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e618bdac8190be291468b7d977bb |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.