Triple
T19507759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K Street SW |
E488068
|
entity |
| Predicate | usesAddressSystem |
P1216
|
FINISHED |
| Object | Washington, D.C. addressing system |
—
|
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: Washington, D.C. addressing system | Statement: [K Street SW, usesAddressSystem, Washington, D.C. addressing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAddressSystem Context triple: [K Street SW, usesAddressSystem, Washington, D.C. addressing system]
-
A.
usesAddressingSystem
chosen
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
B.
hasPostalAddressSystem
Indicates that an entity possesses or is served by an organized system for assigning and managing postal addresses.
-
C.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
D.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
E.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635130e708190bb3d70e1abbade2a |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.