Triple
T3539615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillermo Rigondeaux |
E74850
|
entity |
| Predicate | trainingBackground |
P42544
|
FINISHED |
| Object | Cuban boxing school |
—
|
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: Cuban boxing school | Statement: [Guillermo Rigondeaux, trainingBackground, Cuban boxing school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingBackground Context triple: [Guillermo Rigondeaux, trainingBackground, Cuban boxing school]
-
A.
trainingBase
Indicates that one entity serves as the training base, site, or facility where another entity receives training or instruction.
-
B.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
C.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
D.
trainingUse
Indicates that something is used for training purposes, such as preparing, educating, or improving the skills or performance of an entity.
-
E.
trainingGroundFor
chosen
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbccbbb5c8190a951754dda5fc642 |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.