Triple
T13475465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MALAYSIAN THREE SEVEN ZERO |
E318238
|
entity |
| Predicate | dateOfAssociatedIncident |
P830
|
FINISHED |
| Object | 2014-03-08 |
—
|
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: 2014-03-08 | Statement: [MALAYSIAN THREE SEVEN ZERO, dateOfAssociatedIncident, 2014-03-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfAssociatedIncident Context triple: [MALAYSIAN THREE SEVEN ZERO, dateOfAssociatedIncident, 2014-03-08]
-
A.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
B.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
C.
dateOfSituationAddressed
Indicates the date on which the situation, issue, or circumstance being referred to is (or was) addressed or dealt with.
-
D.
allegedInvolvementDate
Indicates the date on which an entity is claimed or reported to have been involved in a particular event or activity, without asserting that the involvement is confirmed.
-
E.
firstAccidentDate
Indicates the date on which an entity experienced its first recorded accident.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.