Triple
T20455050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Anne Hill |
E501752
|
entity |
| Predicate | topographicHighPointOf |
P210
|
FINISHED |
| Object | Seattle core |
—
|
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: Seattle core | Statement: [Queen Anne Hill, topographicHighPointOf, Seattle core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topographicHighPointOf Context triple: [Queen Anne Hill, topographicHighPointOf, Seattle core]
-
A.
countryHighestPointAccess
Indicates that an entity has access to, or the ability to reach or utilize, the highest geographical point within a specified country.
-
B.
highestPoint
chosen
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
D.
trailHighPointOf
Indicates that one location is the highest elevation point along a specified trail or route.
-
E.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a0dd188190ab6cbb387d9c0c1d |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.