Triple
T16957367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coroner’s Court of Singapore |
E411339
|
entity |
| Predicate | mayMake |
P5771
|
FINISHED |
| Object | recommendations to prevent similar deaths |
—
|
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: recommendations to prevent similar deaths | Statement: [Coroner’s Court of Singapore, mayMake, recommendations to prevent similar deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayMake Context triple: [Coroner’s Court of Singapore, mayMake, recommendations to prevent similar deaths]
-
A.
canMake
chosen
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
B.
mayCompose
Indicates that an entity has permission or authority to create or write another entity (such as a document, message, or composition).
-
C.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
D.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01d34d08190a73ce48e9988bd97 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.