Triple
T13074843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inova Mount Vernon Hospital |
E329544
|
entity |
| Predicate | hasRehabilitationCenter |
P10262
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Inova Mount Vernon Hospital, hasRehabilitationCenter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRehabilitationCenter Context triple: [Inova Mount Vernon Hospital, hasRehabilitationCenter, yes]
-
A.
hasTraumaCenter
Indicates that an entity (such as a hospital or facility) includes or is equipped with a designated trauma center capable of providing specialized emergency care for severe injuries.
-
B.
hasMedicalCenter
chosen
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
C.
hasInformationCenterFor
Indicates that one entity serves as an information center dedicated to providing information or services related to another entity.
-
D.
housingLocation
Indicates the place or area where a person or group resides or is accommodated.
-
E.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98117209081908272021013df2222 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.