Triple
T33210981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Castle |
E850156
|
entity |
| Predicate | careerTrajectory |
P26658
|
FINISHED |
| Object | meteoric rise |
—
|
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: meteoric rise | Statement: [Joe Castle, careerTrajectory, meteoric rise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careerTrajectory Context triple: [Joe Castle, careerTrajectory, meteoric rise]
-
A.
careerPath
chosen
Indicates the progression or sequence of roles, positions, or occupations that an individual follows over time in their professional life.
-
B.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
-
C.
careerStart
Indicates the point in time when an entity begins its professional career or main occupational activity.
-
D.
careerImpact
Indicates how one entity influences or changes another entity’s professional trajectory, opportunities, or outcomes.
-
E.
careerDevelopment
Indicates a relationship where one entity supports, influences, or engages in the growth, progression, or improvement of another entity’s professional path or skills.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:30 a.m.