Triple
T26669534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour du Mont d’Or |
E672285
|
entity |
| Predicate | panoramicDirection |
P29603
|
FINISHED |
| Object | surrounding valleys and hills |
—
|
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: surrounding valleys and hills | Statement: [Tour du Mont d’Or, panoramicDirection, surrounding valleys and hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: panoramicDirection Context triple: [Tour du Mont d’Or, panoramicDirection, surrounding valleys and hills]
-
A.
hasPanoramicView
chosen
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
panoramaDesigner
Indicates a relationship where an entity is responsible for designing or creating panoramic views or panorama-related content for another entity or context.
-
C.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
D.
gazeDirection
Indicates the direction in which an entity is looking or focusing its visual attention.
-
E.
panoramaCreatedFor
Indicates that a panorama (a wide-angle composite image or view) has been generated or produced specifically for a particular entity or context.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f616fdc73c81909243f5f64d36a698 |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:12 a.m.