Triple
T20921272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N scale |
E515213
|
entity |
| Predicate | typicalMinimumRadius |
P135329
|
FINISHED |
| Object | approximately 9 inches (about 228 mm) |
—
|
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: approximately 9 inches (about 228 mm) | Statement: [N scale, typicalMinimumRadius, approximately 9 inches (about 228 mm)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMinimumRadius Context triple: [N scale, typicalMinimumRadius, approximately 9 inches (about 228 mm)]
-
A.
minimumRadiusOfCurves
Indicates the smallest allowable radius for any curve in a path, track, or route associated with the subject.
-
B.
hasRadiusRange
chosen
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
C.
recommendedMinimumSize
Indicates the smallest size that is advised or suggested as a minimum for something to be used or considered appropriate.
-
D.
neighborhoodRadius
Indicates the maximum distance around a reference entity within which other entities are considered to be in its neighborhood.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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.