Triple
T30765205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Mill community |
E783347
|
entity |
| Predicate | postalServiceCityDesignation |
P19163
|
FINISHED |
| Object | Portland, Oregon |
—
|
NE NERFINISHED |
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: Portland, Oregon | Statement: [Cedar Mill community, postalServiceCityDesignation, Portland, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalServiceCityDesignation Context triple: [Cedar Mill community, postalServiceCityDesignation, Portland, Oregon]
-
A.
postalServiceDesignation
chosen
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
B.
hasPostalServiceCity
Indicates that a location is served by or associated with a particular city’s postal service.
-
C.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
-
D.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
E.
postalDepiction
Indicates a relationship where one entity is depicted or represented on a postal item (such as a stamp, envelope, or postcard).
- 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_69f68fbcebe081908f256d1f3dea5d34 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:39 p.m.