Triple
T21829967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guatemalan Civil War |
E538964
|
entity |
| Predicate | estimatedDisappeared |
P87238
|
FINISHED |
| Object | around 40,000 people |
—
|
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: around 40,000 people | Statement: [Guatemalan Civil War, estimatedDisappeared, around 40,000 people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDisappeared Context triple: [Guatemalan Civil War, estimatedDisappeared, around 40,000 people]
-
A.
timeOfDisappearance
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
B.
disappearanceStatus
Indicates the state or condition of whether and how something or someone has gone missing or ceased to be present.
-
C.
disappearedDuring
Indicates that an entity ceased to be observable or present during the time span or event associated with another entity.
-
D.
disappearanceOf
Indicates that one entity ceases to exist, be present, or be observable in relation to another entity, context, or time.
-
E.
missingPersonsEstimate
chosen
Indicates an estimated number of people who are unaccounted for or reported missing in a given context or 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0913554508190b81347f01d3903e8 |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.