Triple
T22278414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakri crossroads action |
E550666
|
entity |
| Predicate | placeInWiderEvent |
P7679
|
FINISHED |
| Object | fall of Malaya |
—
|
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: fall of Malaya | Statement: [Bakri crossroads action, placeInWiderEvent, fall of Malaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInWiderEvent Context triple: [Bakri crossroads action, placeInWiderEvent, fall of Malaya]
-
A.
placeNamedAfterEvent
Indicates that a place derives its name from a specific historical event or occurrence.
-
B.
posedAtEvent
Indicates that an entity assumed a particular pose or posture during a specified event.
-
C.
coversEvent
chosen
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
D.
anchorEvent
Indicates that one event serves as a fixed reference point in time or context for another event or set of events.
-
E.
coordinateEvent
Indicates overseeing and organizing the planning, logistics, and execution of an event in collaboration with involved parties.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea96948819081c1ae6c7b11ab62 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.