Triple
T19232791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sook Ching |
E480911
|
entity |
| Predicate | postwarProceeding |
P13560
|
FINISHED |
| Object | war crimes trials in Singapore |
—
|
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: war crimes trials in Singapore | Statement: [Sook Ching, postwarProceeding, war crimes trials in Singapore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postwarProceeding Context triple: [Sook Ching, postwarProceeding, war crimes trials in Singapore]
-
A.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
B.
postwarActivity
chosen
Indicates activities, roles, or developments associated with an entity specifically in the period following a war or major conflict.
-
C.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
-
D.
postWarOrder
Indicates the arrangement of political, economic, and social relations established among actors after a war has ended.
-
E.
postWarPosition
Indicates the role, status, or position an entity held in the period following a war.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9fa7348190947129273d19c9a7 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:25 p.m.