Triple
T2372955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Charter on Space and Major Disasters |
E46130
|
entity |
| Predicate | supportsDisasterType |
P38752
|
FINISHED |
| Object | floods |
—
|
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: floods | Statement: [International Charter on Space and Major Disasters, supportsDisasterType, floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDisasterType Context triple: [International Charter on Space and Major Disasters, supportsDisasterType, floods]
-
A.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
C.
hasReliefEffortFrom
Indicates that a party receives assistance or support through a relief effort provided by another party.
-
D.
supportsMissionType
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
E.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:56 p.m.