Triple
T20921264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N scale |
E515213
|
entity |
| Predicate | typicalScaleRatio |
P30460
|
FINISHED |
| Object | 1:160 |
—
|
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:160 | Statement: [N scale, typicalScaleRatio, 1:160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScaleRatio Context triple: [N scale, typicalScaleRatio, 1:160]
-
A.
associatedScale
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
-
B.
areaScale
chosen
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
C.
typicalUseRatio
Indicates the proportion or share in which something is commonly or normally used relative to other possible uses or components.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
representationRatio
Indicates the proportional relationship between how much one entity represents, depicts, or stands in for another relative to some whole or reference amount.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f64e56bc81908aa86f2176fcc0db |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.