Triple
T7537667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | José Luis Castillo |
E178189
|
entity |
| Predicate | competitiveRank |
P59486
|
FINISHED |
| Object | world champion at lightweight |
—
|
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: world champion at lightweight | Statement: [José Luis Castillo, competitiveRank, world champion at lightweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveRank Context triple: [José Luis Castillo, competitiveRank, world champion at lightweight]
-
A.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
B.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
C.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
D.
rankingScope
chosen
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8710400819088e430c8c550577e |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.