Triple
T54617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multnomah County |
E1076
|
entity |
| Predicate | gnisID |
P228
|
FINISHED |
| Object | 1163204 |
—
|
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: 1163204 | Statement: [Multnomah County, gnisID, 1163204]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gnisID Context triple: [Multnomah County, gnisID, 1163204]
-
A.
GNISFeatureID
Indicates that an entity is associated with a specific identifier assigned by the U.S. Geological Survey’s Geographic Names Information System (GNIS) to uniquely reference a geographic feature.
-
B.
GNISID
chosen
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
-
C.
mountainSystem
Indicates a relationship where multiple mountains are grouped together as part of the same connected or coherent mountain system or range.
-
D.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
E.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.