Triple
T26036138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelham Bay |
E647555
|
entity |
| Predicate | fireStationNearby |
P62810
|
FINISHED |
| Object | FDNY Engine 89/Ladder 50 |
—
|
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: FDNY Engine 89/Ladder 50 | Statement: [Pelham Bay, fireStationNearby, FDNY Engine 89/Ladder 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireStationNearby Context triple: [Pelham Bay, fireStationNearby, FDNY Engine 89/Ladder 50]
-
A.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
-
B.
nearbyWildfire
Indicates that a wildfire is occurring close enough to a given location or entity to be considered in its immediate vicinity.
-
C.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
D.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
E.
hasFireServicesFrom
chosen
Indicates that one entity receives fire protection or firefighting services from another entity.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061e95848190b6a47fd49280ad1c |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:08 a.m.