Triple
T4356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland, Oregon, United States |
E84
|
entity |
| Predicate | elevationAboveSeaLevel |
P221
|
FINISHED |
| Object | 15 m |
—
|
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: 15 m | Statement: [Portland, Oregon, United States, elevationAboveSeaLevel, 15 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationAboveSeaLevel Context triple: [Portland, Oregon, United States, elevationAboveSeaLevel, 15 m]
-
A.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
D.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
-
E.
landArea
Indicates the total surface area of a piece of land associated with an entity, typically measured in standardized units (e.g., square meters, hectares).
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23c24b3d08190a714126292fd5479 |
completed | Feb. 28, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69a23998af288190855f0456740cbd51 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.