Triple
T36013168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmogorov microscales |
E1041766
|
entity |
| Predicate | symbolForTimeScale |
P177017
|
FINISHED |
| Object | τη |
—
|
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: τη | Statement: [Kolmogorov microscales, symbolForTimeScale, τη]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForTimeScale Context triple: [Kolmogorov microscales, symbolForTimeScale, τη]
-
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.
focusesOnTimeScale
Indicates that something is concerned with, analyzes, or is defined in terms of a particular time scale or temporal granularity.
-
C.
timeSymbol
chosen
Indicates a symbolic or notational representation that stands for a specific point in time, duration, or temporal concept.
-
D.
timeScaleCategory
Indicates the classification of an event or process based on the temporal scale or duration over which it occurs.
-
E.
timeScaleClass
Indicates the classification of a temporal scale or granularity at which an event, process, or relationship is considered or analyzed.
- 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_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:07 p.m.