Triple
T26675472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castillo vs. Corrales I |
E672442
|
entity |
| Predicate | titleUnificationBout |
P180006
|
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: [Castillo vs. Corrales I, titleUnificationBout, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUnificationBout Context triple: [Castillo vs. Corrales I, titleUnificationBout, true]
-
A.
firstBoutTitleOnTheLine
Indicates that in the first bout of an event, a championship title is at stake for the competitors involved.
-
B.
titleFightsConsistOf
Indicates that a set of title fights is composed of, or made up from, specific individual fights.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
battedTitle
Indicates that one entity served as the title or headline for another entity in a way that was prominently featured or “batted” (highlighted) in a media or publication context.
-
E.
titleAffirms
Indicates that a title explicitly asserts, confirms, or supports the truth or validity of a particular claim, idea, or relationship.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 27, 2026, 3:16 a.m.