Triple
T30141664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia City, Seattle |
E766144
|
entity |
| Predicate | hasCommercialCore |
P202960
|
FINISHED |
| Object | Rainier Avenue South |
—
|
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: Rainier Avenue South | Statement: [Columbia City, Seattle, hasCommercialCore, Rainier Avenue South]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommercialCore Context triple: [Columbia City, Seattle, hasCommercialCore, Rainier Avenue South]
-
A.
hasCommercialServices
Indicates that one entity provides or offers commercial services to another entity or within a specified context.
-
B.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
C.
hasCommercialField
Indicates that one entity possesses or is associated with a commercial-related field, area, or domain in relation to another entity.
-
D.
hasCommercialVariant
Indicates that an entity has a related version that is produced, marketed, or sold commercially.
-
E.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
- F. None of above. chosen
Provenance (4 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
| PDg | Predicate description generation | batch_6a00d6af4c588190a52f727a9dabd3dc |
completed | May 10, 2026, 7:04 p.m. |
Created at: April 29, 2026, 7:18 p.m.