Triple
T10746454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ylenia Carrisi |
E253461
|
entity |
| Predicate | disappearanceStatus |
P95770
|
FINISHED |
| Object | missing, presumed dead |
—
|
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: missing, presumed dead | Statement: [Ylenia Carrisi, disappearanceStatus, missing, presumed dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disappearanceStatus Context triple: [Ylenia Carrisi, disappearanceStatus, missing, presumed dead]
-
A.
disappearance
Indicates that an entity ceases to be present, visible, or detectable in a given context or location.
-
B.
disappearedDuring
Indicates that an entity ceased to be observable or present during the time span or event associated with another entity.
-
C.
placeOfDisappearance
Indicates the location where an entity was last seen or went missing.
-
D.
timeOfDisappearance
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
E.
disappearanceCause
Indicates the reason or factor that led to an entity’s disappearance.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b85d9c8190a66f536e2f22ed04 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:15 p.m.