Triple
T28037128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Canterbury |
E708439
|
entity |
| Predicate | hasUnfulfilledAmbitions |
P159664
|
FINISHED |
| Object | becoming a psychologist |
—
|
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: becoming a psychologist | Statement: [Tim Canterbury, hasUnfulfilledAmbitions, becoming a psychologist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnfulfilledAmbitions Context triple: [Tim Canterbury, hasUnfulfilledAmbitions, becoming a psychologist]
-
A.
hasAmbitionLevel
Indicates that an entity possesses a certain degree or intensity of ambition, typically quantified or categorized as a level.
-
B.
aspiredTo
chosen
Indicates that one entity had a strong desire or ambition to achieve, become, or obtain the other entity.
-
C.
hasFictionalGoal
Indicates that an entity is associated with a goal or objective that exists only within a fictional, imagined, or narrative context.
-
D.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
E.
hasNotableMission
Indicates that an entity is associated with a mission or undertaking that is considered significant or noteworthy.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 8:22 p.m.