Triple
T17322345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PERMA model of well-being |
E420592
|
entity |
| Predicate | includesBoth |
P1393
|
FINISHED |
| Object | hedonic aspects of well-being |
—
|
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: hedonic aspects of well-being | Statement: [PERMA model of well-being, includesBoth, hedonic aspects of well-being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBoth Context triple: [PERMA model of well-being, includesBoth, hedonic aspects of well-being]
-
A.
includesRight
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
B.
includesRange
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
-
C.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
-
E.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d01e2c8190a358dace420d4575 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.