Triple
T35652532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Sulawesi earthquake and tsunami |
E1030190
|
entity |
| Predicate | missingPeople |
P87238
|
FINISHED |
| Object | over 1000 |
—
|
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: over 1000 | Statement: [2018 Sulawesi earthquake and tsunami, missingPeople, over 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missingPeople Context triple: [2018 Sulawesi earthquake and tsunami, missingPeople, over 1000]
-
A.
placeOfDisappearance
Indicates the location where an entity was last seen or went missing.
-
B.
hasMissingPersonCase
Indicates that an entity is involved in or associated with a missing person case.
-
C.
lostBodyDueTo
Indicates that an entity no longer possesses a body as a result of a specified cause or event.
-
D.
missingPersonsEstimate
chosen
Indicates an estimated number of people who are unaccounted for or reported missing in a given context or event.
-
E.
intendedDestinationAtTimeOfDisappearance
Indicates the location or place an entity was planning to go to at the specific time when it disappeared.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.