Triple
T26411961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floyd Mayweather Jr. vs. Canelo Álvarez |
E663983
|
entity |
| Predicate | judgeWith114-114Card |
P68922
|
FINISHED |
| Object | C. J. Ross |
—
|
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: C. J. Ross | Statement: [Floyd Mayweather Jr. vs. Canelo Álvarez, judgeWith114-114Card, C. J. Ross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judgeWith114-114Card Context triple: [Floyd Mayweather Jr. vs. Canelo Álvarez, judgeWith114-114Card, C. J. Ross]
-
A.
judgeFrom
Indicates that one entity forms an opinion, evaluation, or conclusion about something based on another specified source, basis, or perspective.
-
B.
judgedAs
Indicates that one entity evaluates or forms an opinion about another entity according to some criteria or standard.
-
C.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
D.
judgedOn
Indicates that an entity is evaluated or assessed based on a specified criterion, standard, or aspect.
-
E.
judgeAlongside
chosen
Indicates that one entity serves as a judge together with another entity in the same evaluative context or proceeding.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611325fd48190898639883fb113fd |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:38 p.m.