Triple
T10355816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laban effort theory |
E243995
|
entity |
| Predicate | coreDimension |
P3633
|
FINISHED |
| Object | Weight |
—
|
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: Weight | Statement: [Laban effort theory, coreDimension, Weight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreDimension Context triple: [Laban effort theory, coreDimension, Weight]
-
A.
dimensionCharacteristic
Indicates that one entity specifies or describes a dimensional property or measurement characteristic of another entity.
-
B.
dimensionStatement
Indicates that a statement specifies the measured size, extent, or dimensional properties of an entity or relationship.
-
C.
dimensionVariant
Indicates a relationship where one entity is a variant or alternative version of another with respect to certain dimensions or configurable attributes.
-
D.
dimension
chosen
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
E.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
- 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_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. |
Created at: April 6, 2026, 11:58 a.m.