Triple
T10355784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laban movement analysis |
E243994
|
entity |
| Predicate | spaceConcept |
P93838
|
FINISHED |
| Object | kinesphere |
—
|
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: kinesphere | Statement: [Laban movement analysis, spaceConcept, kinesphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceConcept Context triple: [Laban movement analysis, spaceConcept, kinesphere]
-
A.
space
Indicates that one entity is located in, occupies, or is associated with a particular physical or conceptual space relative to another.
-
B.
spaceSegment
Indicates that one entity is a space-based component or portion of a larger system or infrastructure associated with the other entity.
-
C.
spaceEnvironment
Indicates that the relationship or action occurs within, is influenced by, or pertains to the conditions and context of outer space or a space-related environment.
-
D.
spacecraft
Indicates that an entity is a vehicle or object designed to travel or operate in outer space.
-
E.
spaceflight
Indicates the undertaking of travel or transportation beyond Earth’s atmosphere, typically via spacecraft operating in outer space.
- 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.