Triple
T92710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer Courthouse Square |
E1863
|
entity |
| Predicate | hasAddress |
P4379
|
FINISHED |
| Object | 701 SW 6th Avenue, Portland, 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: 701 SW 6th Avenue, Portland, Oregon | Statement: [Pioneer Courthouse Square, hasAddress, 701 SW 6th Avenue, Portland, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddress Context triple: [Pioneer Courthouse Square, hasAddress, 701 SW 6th Avenue, Portland, Oregon]
-
A.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
B.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
C.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
D.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
E.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a2512cc3108190aefe5e624312f7d0 |
completed | Feb. 28, 2026, 2:21 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.