Triple
T22650879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. George Hill |
E559087
|
entity |
| Predicate | hasVantagePointOver |
P127904
|
FINISHED |
| Object | surrounding area |
—
|
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 area | Statement: [St. George Hill, hasVantagePointOver, surrounding area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVantagePointOver Context triple: [St. George Hill, hasVantagePointOver, surrounding area]
-
A.
hasViewingPointFor
chosen
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
hasViewpointStatus
Indicates that an entity holds a particular evaluative or perspectival status (e.g., stance, opinion, or viewpoint classification) with respect to something.
-
C.
hasViewpointType
Indicates that something is associated with or characterized by a particular type or category of viewpoint or perspective.
-
D.
hasSight
Indicates that one entity possesses the ability or capacity to see or visually perceive.
-
E.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703c5538819089d9b5349f26ea6d |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.