Triple
T31913848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDNY Ladder Company 80 |
E814765
|
entity |
| Predicate | isPartOfFDNY |
P183983
|
FINISHED |
| Object | FDNY Ladder Companies |
—
|
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 Ladder Companies | Statement: [FDNY Ladder Company 80, isPartOfFDNY, FDNY Ladder Companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfFDNY Context triple: [FDNY Ladder Company 80, isPartOfFDNY, FDNY Ladder Companies]
-
A.
isPartOfFDNYBoroughCommand
Indicates that one entity functions as a subordinate unit within a specific FDNY borough command structure.
-
B.
belongsToFireDepartment
chosen
Indicates that an entity is a member of, affiliated with, or under the authority of a specific fire department.
-
C.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
-
D.
locatedInFormerBorough
Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
-
E.
operatedInBorough
Indicates that an entity conducted its operations or activities within the geographic area of a specific borough.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 1, 2026, 12:01 a.m.