Triple
T1911639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camilo Cienfuegos |
E38122
|
entity |
| Predicate | missingStatus |
P127
|
FINISHED |
| Object | body never recovered |
—
|
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: body never recovered | Statement: [Camilo Cienfuegos, missingStatus, body never recovered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missingStatus Context triple: [Camilo Cienfuegos, missingStatus, body never recovered]
-
A.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
C.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
coordinateStatus
Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
-
E.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.