Triple
T29144921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health and Happiness |
E738740
|
entity |
| Predicate | reflectsInterestOfAuthor |
P72119
|
FINISHED |
| Object | personal 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: personal well-being | Statement: [Health and Happiness, reflectsInterestOfAuthor, personal well-being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsInterestOfAuthor Context triple: [Health and Happiness, reflectsInterestOfAuthor, personal well-being]
-
A.
reflectsInterestOfAuthorIn
chosen
Indicates that something expresses or reveals the author’s interest in a particular subject, entity, or topic.
-
B.
reflectsInterestOfArtistIn
Indicates that something expresses or demonstrates the artistic interest or concern of a particular artist.
-
C.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
D.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
E.
subjectRelationToAuthor
Indicates the relationship or connection that the subject has to the author.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 11:39 a.m.