Triple
T8168321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhasset station |
E190750
|
entity |
| Predicate | hasEmergencyPhones |
P37309
|
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: [Manhasset station, hasEmergencyPhones, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyPhones Context triple: [Manhasset station, hasEmergencyPhones, yes]
-
A.
hasNonEmergencyNumber
Indicates that an entity is associated with a phone number intended for non-emergency, routine, or informational contact rather than urgent or emergency situations.
-
B.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
-
C.
emergencyPhoneNumber
chosen
Indicates that the object is a phone number designated for use in emergencies or urgent situations.
-
D.
hasEmergencyIntercoms
Indicates that an entity is equipped with emergency intercom devices available for use in urgent or crisis situations.
-
E.
hasEmergencyCare
Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb466abfe48190b4eb2f23b1e28668 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.