Triple
T27361454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest (NW) Washington, D.C. |
E685834
|
entity |
| Predicate | streetAddressSuffix |
P162549
|
FINISHED |
| Object | NW |
—
|
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: NW | Statement: [Northwest (NW) Washington, D.C., streetAddressSuffix, NW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetAddressSuffix Context triple: [Northwest (NW) Washington, D.C., streetAddressSuffix, NW]
-
A.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
B.
namedAfterStreet
Indicates that an entity’s name is derived from or taken in honor of a particular street.
-
C.
streetOrArea
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
D.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c23b91c8190a430caf3791f932e |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 11:54 a.m.