Triple
T13811358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Quest |
E331896
|
entity |
| Predicate | fieldOfViewApproximate |
P2524
|
FINISHED |
| Object | ~100 degrees |
—
|
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: ~100 degrees | Statement: [Oculus Quest, fieldOfViewApproximate, ~100 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfViewApproximate Context triple: [Oculus Quest, fieldOfViewApproximate, ~100 degrees]
-
A.
hasFieldOfView
chosen
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
B.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
C.
intendedViewingDistance
Indicates the distance at which something is meant or designed to be viewed or observed.
-
D.
focalLength
Indicates the distance between a lens or mirror and its focal point, determining how strongly it converges or diverges light.
-
E.
fieldOfViewComparedToHubble
Indicates how the field of view of one instrument, observation, or image compares in size or coverage to that of the Hubble Space Telescope.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026ff6b481908066d6bf27064417 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.