Triple
T18335916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian Yates |
E439268
|
entity |
| Predicate | preContestCondition |
P14814
|
FINISHED |
| Object | extreme muscular definition |
—
|
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: extreme muscular definition | Statement: [Dorian Yates, preContestCondition, extreme muscular definition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preContestCondition Context triple: [Dorian Yates, preContestCondition, extreme muscular definition]
-
A.
isEarlyContestIn
Indicates that a contest or competition occurs in the early phase or initial stage within a specified larger event, period, or context.
-
B.
losesContestTo
Indicates that one participant is defeated by another in a contest or competition.
-
C.
precondition
chosen
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
D.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
E.
preDebateStage
Indicates that an entity is at a stage or phase that occurs before a debate takes place.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecd759481909703ed2d0d68199f |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.