Triple
T15525214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miguel Tejada |
E369064
|
entity |
| Predicate | bannedSubstanceSuspension |
P72152
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Miguel Tejada, bannedSubstanceSuspension, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedSubstanceSuspension Context triple: [Miguel Tejada, bannedSubstanceSuspension, yes]
-
A.
bannedForPEDs
chosen
Indicates that an entity (typically an athlete) is prohibited from participating due to violations involving performance-enhancing drugs.
-
B.
suspendedBy
Indicates that one entity has temporarily halted, removed, or placed another entity in an inactive or pending state, typically as an enforcement or administrative action.
-
C.
suspendedFrom
Indicates that one entity is hanging or held up in the air by being attached to another supporting entity.
-
D.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
E.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04145178481909fb0339a79d4239e |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.