Triple
T37417425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meridian Township Fire Department |
E929752
|
entity |
| Predicate | hasPrimaryResponseType |
P92192
|
FINISHED |
| Object | all-hazards emergency response |
—
|
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: all-hazards emergency response | Statement: [Meridian Township Fire Department, hasPrimaryResponseType, all-hazards emergency response]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryResponseType Context triple: [Meridian Township Fire Department, hasPrimaryResponseType, all-hazards emergency response]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasReplyType
chosen
Indicates that an entity’s reply or response is of a specified type or category.
-
C.
hasPrimarySourceType
Indicates that something is associated with a main or original type of source from which information or evidence is directly obtained.
-
D.
hasPrimaryAccessType
Indicates that an entity is associated with its main or default mode or category of access.
-
E.
hasResponseMode
Indicates that an entity operates or behaves according to a particular mode or style of responding.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.