Triple
T28019789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C Track |
E707653
|
entity |
| Predicate | hasScaleRatio |
P14260
|
FINISHED |
| Object | 1:87 |
—
|
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: 1:87 | Statement: [C Track, hasScaleRatio, 1:87]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScaleRatio Context triple: [C Track, hasScaleRatio, 1:87]
-
A.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
B.
hasScaleSize
Indicates that one entity possesses a scale characterized by a particular size or magnitude in relation to another entity or value.
-
C.
hasScaleHeight
Indicates the characteristic vertical distance over which a quantity (such as pressure, density, or concentration) decreases by a fixed factor in a stratified medium.
-
D.
hasScaleFactorForm
chosen
Indicates that one entity is represented as a scaled version or proportional form of another, typically via a specific scale factor.
-
E.
isScaleInvariant
Indicates that a property, equation, or system remains unchanged when all relevant dimensions or variables are uniformly scaled by a common factor.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 8:09 p.m.