Triple
T16336474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRISM |
E396690
|
entity |
| Predicate | viewConfiguration |
P79764
|
FINISHED |
| Object | nadir view |
—
|
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: nadir view | Statement: [PRISM, viewConfiguration, nadir view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewConfiguration Context triple: [PRISM, viewConfiguration, nadir view]
-
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.
displayConfiguration
chosen
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
D.
viewGeometry
Indicates a relationship where a particular viewpoint or camera setup defines how a scene’s geometry is projected, framed, or visually represented.
-
E.
viewType
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e3af7881908a3116c41ed69115 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.