Triple
T14074267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse Brown VA Medical Center |
E338690
|
entity |
| Predicate | primaryClientGroup |
P112711
|
FINISHED |
| Object | United States military veterans |
—
|
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: United States military veterans | Statement: [Jesse Brown VA Medical Center, primaryClientGroup, United States military veterans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryClientGroup Context triple: [Jesse Brown VA Medical Center, primaryClientGroup, United States military veterans]
-
A.
primaryClient
Indicates that one entity serves as the main or most important client associated with another entity.
-
B.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
C.
primaryUserGroups
Indicates the main or default user groups to which an entity (such as a user account) is assigned.
-
D.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
E.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.