Triple
T18335901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian Yates |
E439268
|
entity |
| Predicate | turnedProIn |
P9282
|
FINISHED |
| Object | late 1980s |
—
|
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: late 1980s | Statement: [Dorian Yates, turnedProIn, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnedProIn Context triple: [Dorian Yates, turnedProIn, late 1980s]
-
A.
turnedPro
chosen
Indicates that an individual transitioned from amateur status to professional status in a particular field or activity.
-
B.
turnsIn
Indicates that an entity submits or hands over something, typically work or an item, to another party or authority.
-
C.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
D.
confirmedFor
Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
-
E.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
- 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.