Triple
T12921593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unidad de Protección Civil de Tláhuac |
E309134
|
entity |
| Predicate | tipoDeEmergenciasAtendidas |
P77203
|
FINISHED |
| Object | sismos |
—
|
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: sismos | Statement: [Unidad de Protección Civil de Tláhuac, tipoDeEmergenciasAtendidas, sismos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeEmergenciasAtendidas Context triple: [Unidad de Protección Civil de Tláhuac, tipoDeEmergenciasAtendidas, sismos]
-
A.
typeOfEmergencyService
Indicates the specific category or kind of emergency service associated with or provided in a given situation.
-
B.
emergencyTypesCovered
chosen
Indicates that certain kinds of emergencies are included within the scope of coverage, protection, or response defined by the relationship.
-
C.
typeOfRescue
Indicates the specific method or category of rescue operation performed in a rescue event.
-
D.
resultOfEmergency
Indicates that something occurs or exists as a direct consequence of an emergency situation or event.
-
E.
typeOfCrisis
Indicates the specific category or nature of a crisis that an entity is experiencing or associated with.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e7f6e881908c7bb12283898c80 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.