Triple
T19652343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Airmont |
E471845
|
entity |
| Predicate | hasEmergencyMedicalServicesFrom |
P90151
|
FINISHED |
| Object | regional EMS providers |
—
|
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: regional EMS providers | Statement: [Village of Airmont, hasEmergencyMedicalServicesFrom, regional EMS providers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyMedicalServicesFrom Context triple: [Village of Airmont, hasEmergencyMedicalServicesFrom, regional EMS providers]
-
A.
hasEmergencyServiceProvider
chosen
Indicates that an entity is associated with or served by a specific emergency service provider (such as police, fire, or medical services).
-
B.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
-
C.
hasEmergencyCare
Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
-
D.
hasFireServicesFrom
Indicates that one entity receives fire protection or firefighting services from another entity.
-
E.
emergencyServicesRegion
Indicates the geographic region within which specific emergency services are responsible for responding to incidents.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414327d88190826ab9511f2f8e48 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.