Triple
T6218941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knights Valley |
E139061
|
entity |
| Predicate | geographicPosition |
P3227
|
FINISHED |
| Object | northeastern Sonoma County |
—
|
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: northeastern Sonoma County | Statement: [Knights Valley, geographicPosition, northeastern Sonoma County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicPosition Context triple: [Knights Valley, geographicPosition, northeastern Sonoma County]
-
A.
geographicContext
chosen
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
B.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
C.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a481908190a1418d9fcfaf8137 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.