Triple
T25307479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CalVet |
E634518
|
entity |
| Predicate | operatesVeteransHomesIn |
P152229
|
FINISHED |
| Object | Yountville, California |
—
|
NE NERFINISHED |
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: Yountville, California | Statement: [CalVet, operatesVeteransHomesIn, Yountville, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesVeteransHomesIn Context triple: [CalVet, operatesVeteransHomesIn, Yountville, California]
-
A.
operatedHospitalsIn
Indicates that an entity managed or ran the operations of one or more hospitals located in a specified place or context.
-
B.
agingFacility
Indicates that a facility is undergoing or associated with the process of aging, deterioration, or decline in condition over time.
-
C.
operatesFacilityInCity
Indicates that an entity manages or runs a particular facility located within a specified city.
-
D.
operatesFacility
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
E.
operatesFacilitiesType
chosen
Indicates that an entity runs or manages facilities of a specified type.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 21, 2026, 1:25 p.m.