Triple
T1150286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derek Nurse |
E23659
|
entity |
| Predicate | fictionalProfession |
P7041
|
FINISHED |
| Object | athlete |
—
|
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: athlete | Statement: [Derek Nurse, fictionalProfession, athlete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalProfession Context triple: [Derek Nurse, fictionalProfession, athlete]
-
A.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
B.
portraysProfession
chosen
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
-
C.
visionaryOccupation
Indicates that an entity holds an occupation or role characterized by forward-thinking, innovative, or visionary activities or responsibilities.
-
D.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
E.
creatorOccupation
Indicates the professional role or job that the creator of an entity holds or held.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.