Triple
T10355780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laban movement analysis |
E243994
|
entity |
| Predicate | dimensionOfEffort |
P93837
|
FINISHED |
| Object | Space effort |
—
|
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: Space effort | Statement: [Laban movement analysis, dimensionOfEffort, Space effort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionOfEffort Context triple: [Laban movement analysis, dimensionOfEffort, Space effort]
-
A.
hasPlanningEffort
Indicates that an entity is associated with a required or invested amount of planning work or preparation effort.
-
B.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
C.
workLength
Indicates the duration or length of time associated with a particular work or task.
-
D.
productivityLevel
Indicates the degree or intensity of how much useful output or work an entity produces over a given period or context.
-
E.
difficultyRelativeTo
Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e953d4888190b7ca0ac932349dbf |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:58 a.m.