Triple
T36013177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmogorov microscales |
E1041766
|
entity |
| Predicate | dimensionOfVelocityScale |
P1938
|
FINISHED |
| Object | velocity |
—
|
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: velocity | Statement: [Kolmogorov microscales, dimensionOfVelocityScale, velocity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionOfVelocityScale Context triple: [Kolmogorov microscales, dimensionOfVelocityScale, velocity]
-
A.
dimensionOfTimeScale
Indicates that one entity specifies the temporal dimension or granularity (e.g., seconds, days, years) used as the time scale for another entity.
-
B.
movementScale
Indicates how the magnitude or intensity of a movement changes relative to a reference level or context.
-
C.
visualScale
Indicates how large or small something appears visually relative to a reference or its actual size.
-
D.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
E.
magnitudeScale
chosen
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.