Triple
T16320546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stabler family |
E396278
|
entity |
| Predicate | servedClientele |
P19115
|
FINISHED |
| Object | local residents of 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: local residents of Alexandria, Virginia | Statement: [Stabler family, servedClientele, local residents of Alexandria, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedClientele Context triple: [Stabler family, servedClientele, local residents of Alexandria, Virginia]
-
A.
servesClientsIn
Indicates that an entity provides services to clients located within a specified geographic area or jurisdiction.
-
B.
categoryOfPeopleServed
chosen
Indicates the type or group of people that are the primary recipients or beneficiaries of a service or activity.
-
C.
professionServed
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
-
D.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
E.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
- 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.