Triple
T28019705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauge 1 |
E707652
|
entity |
| Predicate | scaleRatio |
P124140
|
FINISHED |
| Object | 1:32 |
—
|
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:32 | Statement: [Gauge 1, scaleRatio, 1:32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleRatio Context triple: [Gauge 1, scaleRatio, 1:32]
-
A.
radiusRatio
Indicates the proportional relationship between one radius and another, typically expressing how large one is relative to the other.
-
B.
scaleProperty
Indicates that one entity defines or modifies the scale, magnitude, or proportional sizing used to interpret or represent a property of another entity.
-
C.
sideRatioLength
Indicates the proportional relationship between the lengths of two or more sides in a geometric figure.
-
D.
representationRatio
Indicates the proportional relationship between how much one entity represents, depicts, or stands in for another relative to some whole or reference amount.
-
E.
scaleRelation
chosen
Indicates a relationship where one quantity, object, or representation is proportionally larger or smaller than another according to a specific scale or 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_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:09 p.m.