Triple
T15049009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serenbe |
E379304
|
entity |
| Predicate | wellnessFocus |
P109970
|
FINISHED |
| Object | holistic wellness |
—
|
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: holistic wellness | Statement: [Serenbe, wellnessFocus, holistic wellness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wellnessFocus Context triple: [Serenbe, wellnessFocus, holistic wellness]
-
A.
focusesOnNutrition
Indicates that the subject’s primary attention, activity, or content is centered on nutrition-related topics, practices, or goals.
-
B.
healthTheme
chosen
Indicates that the subject is associated with, focuses on, or is characterized by a particular health-related topic or theme.
-
C.
performanceFocus
Indicates that an entity directs attention or effort toward improving or emphasizing performance in a given context.
-
D.
leadershipFocus
Indicates a relationship where an entity’s attention, priorities, or strategic efforts are directed toward leading, guiding, or influencing others.
-
E.
hasHealthGoal
Indicates that an entity has a specific health-related objective or target it is aiming to achieve.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8f71988190b4fe7f7de4ccb798 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.