Triple
T34676834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satisfaction with Life Scale |
E890513
|
entity |
| Predicate | itemContentType |
P84700
|
FINISHED |
| Object | global evaluative statements about life |
—
|
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: global evaluative statements about life | Statement: [Satisfaction with Life Scale, itemContentType, global evaluative statements about life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: itemContentType Context triple: [Satisfaction with Life Scale, itemContentType, global evaluative statements about life]
-
A.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
B.
describesContentType
chosen
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
C.
offersContentType
Indicates that one entity provides or makes available content of a specified type to another entity or context.
-
D.
mainContentType
Indicates the primary type or category of content associated with an entity or resource.
-
E.
notableContentType
Indicates the type or category of content for which an entity is notable or best known.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f723241a188190bc3e8b2236279511 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.