Triple
T3293265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Island City |
E69149
|
entity |
| Predicate | fireDepartmentCoverage |
P8978
|
FINISHED |
| Object | FDNY companies in Queens |
—
|
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: FDNY companies in Queens | Statement: [Long Island City, fireDepartmentCoverage, FDNY companies in Queens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireDepartmentCoverage Context triple: [Long Island City, fireDepartmentCoverage, FDNY companies in Queens]
-
A.
fireJurisdiction
chosen
Indicates that one entity has official authority and responsibility over fire protection, prevention, or response activities within the area or domain of another entity.
-
B.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
-
C.
fireRescue
Indicates a relationship where one entity performs or is responsible for rescuing people or property from fires or fire-related emergencies involving another entity.
-
D.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
E.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb074f35081909dd3c8a09544b5f1 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.