Triple
T36013167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolmogorov microscales |
E1041766
|
entity |
| Predicate | symbolForLengthScale |
P26854
|
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, symbolForLengthScale, η]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForLengthScale Context triple: [Kolmogorov microscales, symbolForLengthScale, η]
-
A.
hasFundamentalLengthScale
Indicates that there exists a basic, irreducible unit of length that characterizes the scale at which the described entity or theory fundamentally operates.
-
B.
dimensionSymbol
chosen
Indicates a symbolic notation that represents or labels a specific dimension or measurement attribute in a context.
-
C.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
D.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
E.
symbolForConcentrationParameter
Indicates that one entity is used as the symbolic representation of the concentration parameter associated with another entity.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:07 p.m.