Triple
T33911487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS804 |
E869325
|
entity |
| Predicate | timeOfDisappearanceUTC |
P91637
|
FINISHED |
| Object | around 00:30 UTC |
—
|
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 00:30 UTC | Statement: [MS804, timeOfDisappearanceUTC, around 00:30 UTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDisappearanceUTC Context triple: [MS804, timeOfDisappearanceUTC, around 00:30 UTC]
-
A.
timeOfDisappearance
chosen
Indicates the specific time at which an entity disappeared or was last observed to no longer be present.
-
B.
timeOfLossOfContactUTC
Indicates the specific time, expressed in Coordinated Universal Time (UTC), at which contact with an entity was lost.
-
C.
disasterTimeUTC
Indicates the specific date and time, in Coordinated Universal Time (UTC), at which the disaster event occurred or is recorded.
-
D.
yearOfDisappearance
Indicates the specific year in which an entity disappeared or ceased to be present.
-
E.
operatorAtTimeOfDisappearance
Indicates that an operator was responsible for or in control of something at the specific time when a disappearance occurred.
- 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_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:48 a.m.