Triple
T1318112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belton Fire Department |
E28152
|
entity |
| Predicate | hasEquipmentType |
P15250
|
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: [Belton Fire Department, hasEquipmentType, fire engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEquipmentType Context triple: [Belton Fire Department, hasEquipmentType, fire engines]
-
A.
hasWeaponType
Indicates that an entity is associated with or equipped with a specific type or category of weapon.
-
B.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
E.
typeOfEquipmentManaged
chosen
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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c176c89881909e9dc0e34f12f056 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.