Triple
T33911486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS804 |
E869325
|
entity |
| Predicate | timeOfDisappearanceLocal |
P91637
|
FINISHED |
| Object | around 02:30 Eastern European Time |
—
|
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 02:30 Eastern European Time | Statement: [MS804, timeOfDisappearanceLocal, around 02:30 Eastern European Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDisappearanceLocal Context triple: [MS804, timeOfDisappearanceLocal, around 02:30 Eastern European Time]
-
A.
timeOfDisappearance
chosen
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
B.
intendedDestinationAtTimeOfDisappearance
Indicates the location or place an entity was planning to go to at the specific time when it disappeared.
-
C.
operatorAtTimeOfDisappearance
Indicates that an operator was responsible for or in control of something at the specific time when a disappearance occurred.
-
D.
yearOfDisappearance
Indicates the specific year in which an entity disappeared or ceased to be present.
-
E.
placeOfDisappearance
Indicates the location where an entity was last seen or went missing.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 1:48 a.m.