Triple
T33974594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F Street NW |
E871097
|
entity |
| Predicate | usesAddressQuadrant |
P4379
|
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: [F Street NW, usesAddressQuadrant, NW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAddressQuadrant Context triple: [F Street NW, usesAddressQuadrant, NW]
-
A.
usesAddressTo
Indicates that one entity makes use of a particular address (such as a physical, email, or network address) to interact, communicate, or perform an action involving another entity.
-
B.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
C.
canAddress
Indicates that one entity has the ability or permission to direct communication, action, or service toward another entity.
-
D.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
E.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:50 a.m.