Triple
T10830054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlesex Borough Fire Department |
E255593
|
entity |
| Predicate | hasCallSignType |
P4790
|
FINISHED |
| Object | municipal fire department |
—
|
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: municipal fire department | Statement: [Middlesex Borough Fire Department, hasCallSignType, municipal fire department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallSignType Context triple: [Middlesex Borough Fire Department, hasCallSignType, municipal fire department]
-
A.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific entity.
-
B.
hasCallSignPrefix
Indicates that an entity’s call sign begins with a specified prefix.
-
C.
callSignType
chosen
Indicates the classification or category of a call sign associated with an entity or communication.
-
D.
hasCallsignCompanion
Indicates that one entity serves as a companion or associated partner to another entity’s callsign.
-
E.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d74420fa188190b5b3c59e1a9f551d |
completed | April 9, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.