Triple
T16320541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stabler family |
E396278
|
entity |
| Predicate | businessAddress |
P38432
|
FINISHED |
| Object | 105–107 South Fairfax Street, Alexandria, Virginia |
—
|
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: 105–107 South Fairfax Street, Alexandria, Virginia | Statement: [Stabler family, businessAddress, 105–107 South Fairfax Street, Alexandria, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessAddress Context triple: [Stabler family, businessAddress, 105–107 South Fairfax Street, Alexandria, Virginia]
-
A.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
B.
headquartersOfBusiness
Indicates that a location serves as the main administrative center or principal office for a business.
-
C.
addressesWork
Indicates that one entity directs or delivers work-related communication or correspondence to another entity.
-
D.
locationOfEstablishment
chosen
Indicates the place or area where an establishment is situated or operates.
-
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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b5f0f081909a5379deaf0df5d5 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.