Triple
T28390679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flip 3D |
E719147
|
entity |
| Predicate | viewContent |
P11549
|
FINISHED |
| Object | thumbnails of all open windows |
—
|
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: thumbnails of all open windows | Statement: [Flip 3D, viewContent, thumbnails of all open windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewContent Context triple: [Flip 3D, viewContent, thumbnails of all open windows]
-
A.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
B.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
C.
viewTechnologyIn
Indicates that a technology is being viewed, examined, or accessed within a particular context, location, or environment.
-
D.
viewOnCustom
Indicates that one entity is being viewed, accessed, or displayed through a customized or user-defined view associated with another entity.
-
E.
viewType
chosen
Indicates the specific manner or format in which something is displayed, presented, or visually arranged.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cec950881909d89fd56511514a2 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:13 a.m.