Triple
T20610641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle Pad |
E506437
|
entity |
| Predicate | movementRange |
P113583
|
FINISHED |
| Object | 360 degrees |
—
|
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: 360 degrees | Statement: [Circle Pad, movementRange, 360 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementRange Context triple: [Circle Pad, movementRange, 360 degrees]
-
A.
movementScope
chosen
Indicates the extent or range within which a movement or motion is allowed, occurs, or has effect.
-
B.
abilityRange
Indicates the spatial or contextual extent within which an entity’s ability, power, or effect can be applied or is valid.
-
C.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
D.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
E.
displacementRange
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad6f53481908fb242947dda7028 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.