Triple
T10813442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8th Australian Division |
E255161
|
entity |
| Predicate | fateOfPersonnel |
P33525
|
FINISHED |
| Object | many became prisoners of war |
—
|
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: many became prisoners of war | Statement: [8th Australian Division, fateOfPersonnel, many became prisoners of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfPersonnel Context triple: [8th Australian Division, fateOfPersonnel, many became prisoners of war]
-
A.
fateOfMembers
chosen
Indicates the outcome, destiny, or final status experienced by the members of a group or collection.
-
B.
fateOfAllUnits
Indicates the ultimate outcome or final status that applies collectively to all units involved.
-
C.
fateOfLeaders
Indicates the ultimate outcome or destiny that befalls leaders, such as their end, removal, or final status.
-
D.
transferredPersonnelTo
Indicates that one entity moved or reassigned personnel from itself to another entity.
-
E.
militaryPerson
Indicates that the subject is a member of the armed forces or serves in a formal military capacity.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733eba9b48190b4dbe7fe5d8be0a4 |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.