Triple
T25355493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Flaco Explosivo |
E635809
|
entity |
| Predicate | appliedDuringCareerPhase |
P50750
|
FINISHED |
| Object | professional boxing career |
—
|
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: professional boxing career | Statement: [El Flaco Explosivo, appliedDuringCareerPhase, professional boxing career]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedDuringCareerPhase Context triple: [El Flaco Explosivo, appliedDuringCareerPhase, professional boxing career]
-
A.
appliesDuringCareerPhase
chosen
Indicates that something is relevant or in effect only during a specified phase of an entity’s career.
-
B.
chronologicallyPrecedesCareerPhase
Indicates that one career phase occurs earlier in time than another career phase.
-
C.
hasCareerStage
Indicates the specific phase or stage of a person's or entity's professional or occupational progression.
-
D.
isStageInCareerOf
Indicates that one entity represents a particular phase or stage within the professional career of another entity.
-
E.
designedDuringCareerStage
Indicates that something was designed while the person was in a specific stage of their career.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:35 p.m.