Triple
T11722305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yosemite Decimal System |
E278667
|
entity |
| Predicate | definesScaleTo |
P93346
|
FINISHED |
| Object | Class 5 |
—
|
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: Class 5 | Statement: [Yosemite Decimal System, definesScaleTo, Class 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesScaleTo Context triple: [Yosemite Decimal System, definesScaleTo, Class 5]
-
A.
similarScaleTo
Indicates that two entities have comparable magnitude, size, or extent along a given dimension or measurement scale.
-
B.
scalesWith
Indicates that a change in one quantity is systematically associated with a proportional or otherwise dependent change in another quantity.
-
C.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
-
D.
scaleDefinition
chosen
Indicates that an entity specifies the parameters, structure, or measurement system used to define a particular scale.
-
E.
associatedScale
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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.