Triple
T25618111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terence Crawford |
E642213
|
entity |
| Predicate | isMultipleDivisionChampion |
P158920
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Terence Crawford, isMultipleDivisionChampion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultipleDivisionChampion Context triple: [Terence Crawford, isMultipleDivisionChampion, true]
-
A.
hasWonMultipleChampionships
Indicates that the subject has secured championship titles on more than one separate occasion.
-
B.
hasTeamsChampionship
Indicates that an entity has won at least one championship title in a teams-based competition or league.
-
C.
divisionTitlesWonWith
Indicates that one entity has won a specified number of division titles in association with another entity (such as a team, league, or organization).
-
D.
divisionPlayedIn
Indicates that an entity (such as a team or player) participated in or was a member of a particular competitive division.
-
E.
isAFCChampion
Indicates that an entity has won the championship title of the American Football Conference (AFC) in a given season.
- F. None of above. chosen
Provenance (4 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa1e8d948190aab191bfa2226fb8 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5:01 p.m.