Triple
T22329362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Landslide Warning Service |
E551981
|
entity |
| Predicate | warningLevels |
P101040
|
FINISHED |
| Object | multi-level color-coded system |
—
|
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: multi-level color-coded system | Statement: [National Landslide Warning Service, warningLevels, multi-level color-coded system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningLevels Context triple: [National Landslide Warning Service, warningLevels, multi-level color-coded system]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
C.
warningGivenBy
Indicates that one entity issues or delivers a warning to another entity.
-
D.
warningIncludes
chosen
Indicates that a warning message or notice contains or encompasses specific information, elements, or details.
-
E.
warningOutcome
Indicates that a warning event leads to, results in, or is associated with a particular outcome or consequence.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1576ab52c819087563cd778d6bc5e |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.