Triple
T27834376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicole |
E703185
|
entity |
| Predicate | hasPastCondition |
P138411
|
FINISHED |
| Object | drug addiction |
—
|
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: drug addiction | Statement: [Nicole, hasPastCondition, drug addiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastCondition Context triple: [Nicole, hasPastCondition, drug addiction]
-
A.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
-
B.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
C.
hasPriorHistory
chosen
Indicates that an entity has a previously recorded occurrence, condition, or involvement relevant to the current context.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 27, 2026, 5:58 p.m.