Triple
T9027707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EyeSight external display |
E216088
|
entity |
| Predicate | locationOnDevice |
P85950
|
FINISHED |
| Object | front of Apple Vision Pro |
—
|
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: front of Apple Vision Pro | Statement: [EyeSight external display, locationOnDevice, front of Apple Vision Pro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnDevice Context triple: [EyeSight external display, locationOnDevice, front of Apple Vision Pro]
-
A.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
B.
locationOnKit
Indicates that an entity is located on or attached to a specific kit or equipment set.
-
C.
locationDuringUse
Indicates the place or spatial context where an entity is situated specifically while it is being used or in active operation.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
locationServices
Indicates that one entity provides, enables, or manages geographic positioning or place-related functionalities for another entity.
- F. None of above. chosen
Provenance (4 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:07 p.m.