Triple
T36731402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally Rose |
E907346
|
entity |
| Predicate | careerShapedBy |
P11376
|
FINISHED |
| Object | love |
—
|
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: love | Statement: [Sally Rose, careerShapedBy, love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careerShapedBy Context triple: [Sally Rose, careerShapedBy, love]
-
A.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
-
B.
careerPath
Indicates the progression or sequence of roles, positions, or occupations that an individual follows over time in their professional life.
-
C.
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.
-
D.
careerImpact
chosen
Indicates how one entity influences or changes another entity’s professional trajectory, opportunities, or outcomes.
-
E.
careerStart
Indicates the point in time when an entity begins its professional career or main occupational activity.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.