Triple
T7459427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VISTA |
E176206
|
entity |
| Predicate | focalRatio |
P50520
|
FINISHED |
| Object | f/3.25 |
—
|
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: f/3.25 | Statement: [VISTA, focalRatio, f/3.25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focalRatio Context triple: [VISTA, focalRatio, f/3.25]
-
A.
hasFocalRatio
chosen
Indicates a relationship where an optical system is associated with a specific focal ratio (f-number) that characterizes its light-gathering speed and image brightness.
-
B.
hasFocalRatioRange
Indicates that an entity is associated with a range of possible focal ratios, specifying the minimum and maximum f-number values it can have.
-
C.
focalLength
Indicates the distance between a lens or mirror and its focal point, determining how strongly it converges or diverges light.
-
D.
tubeLengthRelativeToFocalLength
Indicates the relationship between an optical system’s tube length and its focal length, typically expressing how long the tube is relative to the focal length.
-
E.
focalLengthExtensionMethod
Indicates a method or technique used to extend or modify the effective focal length in an optical or imaging system.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d332d08190a05c92a00ed09ac6 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:37 p.m.