Triple
T14235474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olivia Crain |
E352864
|
entity |
| Predicate | hasPsychologicalCondition |
P113325
|
FINISHED |
| Object | mental instability (implied) |
—
|
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: mental instability (implied) | Statement: [Olivia Crain, hasPsychologicalCondition, mental instability (implied)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPsychologicalCondition Context triple: [Olivia Crain, hasPsychologicalCondition, mental instability (implied)]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
hasTypicalConditions
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
C.
hadCondition
Indicates that an entity experienced or was diagnosed with a particular medical or health-related condition.
-
D.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
E.
hasMood
Indicates that an entity is experiencing or characterized by a particular emotional or affective state.
- F. None of above. chosen
Provenance (4 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:07 a.m.