Triple
T5646337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Jitra |
E124392
|
entity |
| Predicate | timeSinceWarStart |
P30071
|
FINISHED |
| Object | two days after Japanese invasion of Malaya began |
—
|
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: two days after Japanese invasion of Malaya began | Statement: [Battle of Jitra, timeSinceWarStart, two days after Japanese invasion of Malaya began]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSinceWarStart Context triple: [Battle of Jitra, timeSinceWarStart, two days after Japanese invasion of Malaya began]
-
A.
timeSinceStartOfWar
chosen
Indicates the amount of time that has elapsed since the war began.
-
B.
timeBetweenPeaceAndWarResumption
Indicates the duration of time that elapses between a period of peace and the resumption of war or armed conflict.
-
C.
lastWarStart
Indicates the point in time when the most recent war involving the given entity or entities began.
-
D.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
E.
numberOfDaysOfWar
Indicates the total count of days during which a state of war or active armed conflict persists.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022aa650c819088d9046b82fab631 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.