Triple
T31661311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orangetheory Fitness |
E808007
|
entity |
| Predicate | workoutGoal |
P102263
|
FINISHED |
| Object | improve cardiovascular fitness |
—
|
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: improve cardiovascular fitness | Statement: [Orangetheory Fitness, workoutGoal, improve cardiovascular fitness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workoutGoal Context triple: [Orangetheory Fitness, workoutGoal, improve cardiovascular fitness]
-
A.
hasHealthGoal
chosen
Indicates that an entity has a specific health-related objective or target it is aiming to achieve.
-
B.
movementCoach
Indicates a relationship where one entity serves as a coach or instructor guiding another entity’s physical movement or movement-related skills.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
exerciseOf
Indicates the performance or carrying out of a right, power, function, or activity by an entity.
-
E.
exerciseFocus
Indicates that an exercise or workout activity is primarily directed toward or concentrated on a particular body part, skill, or fitness goal.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:57 p.m.