Triple
T21995959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steven Heathcote |
E543205
|
entity |
| Predicate | hasOccupationAfterRetirement |
P75487
|
FINISHED |
| Object | ballet coach |
—
|
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: ballet coach | Statement: [Steven Heathcote, hasOccupationAfterRetirement, ballet coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationAfterRetirement Context triple: [Steven Heathcote, hasOccupationAfterRetirement, ballet coach]
-
A.
roleAfterRetirement
Indicates the position, function, or status an entity assumes after it has retired from its previous role or activity.
-
B.
hasPastOccupation
Indicates that an entity previously held a particular job, role, or occupation in the past.
-
C.
employedAfter
Indicates that one entity became employed by another entity at a point in time later than a referenced employment event or period.
-
D.
memberLaterOccupation
chosen
Indicates that an individual later held a particular occupation or position after an earlier point in time or role.
-
E.
hadOccupationStatusUntil
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276493bc81908567445e901bc3a7 |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.