Triple
T28019838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K Track |
E707654
|
entity |
| Predicate | targetScale |
P46165
|
FINISHED |
| Object | 1:87 scale |
—
|
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 scale | Statement: [K Track, targetScale, 1:87 scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetScale Context triple: [K Track, targetScale, 1:87 scale]
-
A.
goalScale
Indicates the scale or magnitude at which a goal is defined, measured, or intended to be achieved.
-
B.
targetResolution
Indicates the specific resolution or level of detail that an action, process, or system is intended to achieve or operate at.
-
C.
userScale
Indicates that a user adjusts or sets the scale, size, or zoom level of an object, interface, or content.
-
D.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
-
E.
associatedScale
chosen
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
- 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_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 8:09 p.m.