Triple
T35527188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justin McCully |
E1026702
|
entity |
| Predicate | competedInWeightDivision |
P180898
|
FINISHED |
| Object | UFC heavyweight division |
—
|
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: UFC heavyweight division | Statement: [Justin McCully, competedInWeightDivision, UFC heavyweight division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedInWeightDivision Context triple: [Justin McCully, competedInWeightDivision, UFC heavyweight division]
-
A.
competesInWeightClass
chosen
Indicates that an entity participates in a competition within a specific weight classification or division.
-
B.
competesInDivision
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
C.
performedByWeightClass
Indicates that an action or event is carried out by an entity belonging to a specific weight class.
-
D.
numberOfWeightDivisionsWithWorldTitles
Indicates the count of distinct weight divisions in which an entity has held world championship titles.
-
E.
weightDivisionAbove
Indicates that one entity competes in or belongs to a higher weight division or class than another 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:04 p.m.