Triple
T29092063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nic Sheff |
E734879
|
entity |
| Predicate | hasLivedExperience |
P136773
|
FINISHED |
| Object | substance use disorder |
—
|
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: substance use disorder | Statement: [Nic Sheff, hasLivedExperience, substance use disorder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivedExperience Context triple: [Nic Sheff, hasLivedExperience, substance use disorder]
-
A.
hasPastExperience
chosen
Indicates that an entity has previously engaged in or undergone the specified activity, role, or situation in the past.
-
B.
hasAdultLifeIn
Indicates that an entity spends or experiences its adult stage of life within a specified location or environment.
-
C.
hasIntendedExperience
Indicates that an entity is meant or designed to undergo a particular experience or mental state.
-
D.
hasNotableExperience
Indicates that an entity has a significant or distinguished experience related to another entity or context.
-
E.
hasGlobalExperience
Indicates that an entity possesses experience gained from working, operating, or engaging across multiple countries or international contexts.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 11:06 a.m.