Triple
T23570508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SECAmb |
E580091
|
entity |
| Predicate | hasEmergencyOperationsCentres |
P153206
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SECAmb, hasEmergencyOperationsCentres, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyOperationsCentres Context triple: [SECAmb, hasEmergencyOperationsCentres, yes]
-
A.
hasEmergencyManagementAgency
Indicates that an entity is associated with or served by a specific emergency management agency responsible for planning, coordinating, or responding to emergencies.
-
B.
emergencyOperationsCenterType
Indicates the specific category or classification of an emergency operations center based on its role, scope, or organizational characteristics.
-
C.
hasFireServicesFrom
Indicates that one entity receives fire protection or firefighting services from another entity.
-
D.
hasEmergencySystems
Indicates that the subject is equipped with or includes systems designed to detect, respond to, or manage emergency situations.
-
E.
hasEmergencyPlanningZone
Indicates that an entity is associated with a designated emergency planning zone within which specific preparedness and response measures apply.
- F. None of above. chosen
Provenance (4 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd259e4819094b09f3ed76664ea |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:36 p.m.