Triple
T30765173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Mill |
E783346
|
entity |
| Predicate | countyGovernmentSeatDistance |
P175302
|
FINISHED |
| Object | near Hillsboro, Oregon |
—
|
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: near Hillsboro, Oregon | Statement: [Cedar Mill, countyGovernmentSeatDistance, near Hillsboro, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyGovernmentSeatDistance Context triple: [Cedar Mill, countyGovernmentSeatDistance, near Hillsboro, Oregon]
-
A.
districtHeadquartersDistance
Indicates the distance between a place and its corresponding district headquarters.
-
B.
hasCountyCapitalDistance
Indicates a distance relationship specifying how far a county is from its capital.
-
C.
administrativeCenterDistance
chosen
Indicates the distance between an entity and the administrative center that governs or represents it.
-
D.
distanceFromRegionalCapital
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
E.
parishSeatDistance
Indicates the distance between a parish and its designated parish seat (administrative center).
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: April 29, 2026, 8:39 p.m.