Triple
T6532702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCFEMS |
E152269
|
entity |
| Predicate | equipmentTypeUsed |
P12755
|
FINISHED |
| Object | fire engines |
—
|
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: fire engines | Statement: [DCFEMS, equipmentTypeUsed, fire engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentTypeUsed Context triple: [DCFEMS, equipmentTypeUsed, fire engines]
-
A.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
B.
laterEquipmentType
Indicates that one equipment type occurs or is used at a later time relative to another equipment type.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
hardwareUsedBy
chosen
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
typeOfEquipmentManaged
Indicates the specific kind or category of equipment that an entity is responsible for managing.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbe168881908ffefc4962e2893d |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.