Triple
T27200700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papillion Fire Department |
E683726
|
entity |
| Predicate | appliesSafetyStandard |
P73494
|
FINISHED |
| Object | fire codes and regulations |
—
|
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 codes and regulations | Statement: [Papillion Fire Department, appliesSafetyStandard, fire codes and regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesSafetyStandard Context triple: [Papillion Fire Department, appliesSafetyStandard, fire codes and regulations]
-
A.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
B.
safetyStandardsSimilarTo
Indicates that two entities have safety standards that are comparable or closely aligned in their requirements or rigor.
-
C.
appliesRegulatoryStandard
chosen
Indicates that one entity enforces or uses a specific regulatory standard in relation to another entity or context.
-
D.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
E.
hasSafetyCertificate
Indicates that an entity possesses or has been granted a valid safety certificate.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 9:36 a.m.