Triple
T29598429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulakmonga |
E754370
|
entity |
| Predicate | timeOfMajorDisaster |
P95584
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Bulakmonga, timeOfMajorDisaster, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorDisaster Context triple: [Bulakmonga, timeOfMajorDisaster, 2010]
-
A.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject occurred.
-
B.
timeAfterDisaster
Indicates that a specified time point occurs after the occurrence of a particular disaster event.
-
C.
disasterTimeUTC
chosen
Indicates the specific date and time, in Coordinated Universal Time (UTC), at which the disaster event occurred or is recorded.
-
D.
numberOfMajorShocks
Indicates the count of significant or major shock events associated with an entity or situation.
-
E.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 6:20 p.m.