Triple
T19232584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changi Beach |
E480906
|
entity |
| Predicate | massExecutionDateRange |
P78870
|
FINISHED |
| Object | February 1942 |
—
|
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: February 1942 | Statement: [Changi Beach, massExecutionDateRange, February 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massExecutionDateRange Context triple: [Changi Beach, massExecutionDateRange, February 1942]
-
A.
hasExecutionDate
Indicates that an entity is associated with a specific date on which an execution or carrying out of an action, order, or sentence is scheduled or took place.
-
B.
occurredBetween
chosen
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
C.
someMembersExecutedAt
Indicates that some, but not necessarily all, members of a group were subjected to execution at a particular time or place.
-
D.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
E.
createdBetween
Indicates that something was created within a specified start and end time or date range.
- 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.