Triple
T17952910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya Namaskar |
E448874
|
entity |
| Predicate | hasComponentPose |
P129875
|
FINISHED |
| Object | Pranamasana |
—
|
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: Pranamasana | Statement: [Surya Namaskar, hasComponentPose, Pranamasana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentPose Context triple: [Surya Namaskar, hasComponentPose, Pranamasana]
-
A.
hasHeadPosition
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
-
B.
isJointPosition
Indicates that an entity occupies or specifies a particular position or configuration within a joint (e.g., in a mechanical, robotic, or anatomical system).
-
C.
hasKinematicCenterApprox
Indicates that an entity has an approximate kinematic center location or value associated with it.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
hasComponentStation
Indicates that an entity includes or is associated with a specific station as one of its component parts.
- F. None of above. chosen
Provenance (4 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afad61f481908b34cd24de88983c |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.