Triple
T4892956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Response Coordination Center |
E109606
|
entity |
| Predicate | activatedDuring |
P4341
|
FINISHED |
| Object | major disasters |
—
|
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: major disasters | Statement: [National Response Coordination Center, activatedDuring, major disasters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatedDuring Context triple: [National Response Coordination Center, activatedDuring, major disasters]
-
A.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
B.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
C.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
D.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
-
E.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.