Triple
T4928129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malayan Peoples Anti-Japanese Army |
E110625
|
entity |
| Predicate | receivedSuppliesFrom |
P1704
|
FINISHED |
| Object | British air drops |
—
|
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: British air drops | Statement: [Malayan Peoples Anti-Japanese Army, receivedSuppliesFrom, British air drops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedSuppliesFrom Context triple: [Malayan Peoples Anti-Japanese Army, receivedSuppliesFrom, British air drops]
-
A.
receivedSupportFrom
chosen
Indicates that one entity obtained help, resources, or backing from another entity.
-
B.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
C.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
D.
receivedVolunteersFrom
Indicates that one entity accepted or was provided with volunteers originating from another entity.
-
E.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7036d8e88190bc4be2975160da23 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.