Triple
T19632073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grain Elevators series |
E471294
|
entity |
| Predicate | cameraViewpoint |
P9787
|
FINISHED |
| Object | frontal |
—
|
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: frontal | Statement: [Grain Elevators series, cameraViewpoint, frontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameraViewpoint Context triple: [Grain Elevators series, cameraViewpoint, frontal]
-
A.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
viewpointNear
Indicates that one entity serves as a viewpoint or vantage location that is geographically close to another entity.
-
C.
sceneCenter
Indicates that one entity serves as the central or focal point of a scene in relation to another entity.
-
D.
viewpointFrom
chosen
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
-
E.
observationGeometry
Indicates the spatial and directional configuration between an observer and a target at the time an observation is made.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641036ee881909fdd8170fe4cdac9 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.