Triple
T30373129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarakan operation |
E772604
|
entity |
| Predicate | combatantAllied |
P61211
|
FINISHED |
| Object | Australian Army |
—
|
NE NERFINISHED |
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: Australian Army | Statement: [Tarakan operation, combatantAllied, Australian Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantAllied Context triple: [Tarakan operation, combatantAllied, Australian Army]
-
A.
alliedForces
chosen
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
B.
alliedUnit
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
-
C.
forceTypeAllied
Indicates that the force involved is of an allied type relative to a specified reference side or faction.
-
D.
alliedNationForcesUnderCommand
Indicates that military forces from allied nations are operating under the authority or command structure of a specified commander or entity.
-
E.
alliedForcesComposition
Indicates the makeup and relative proportions of different military or paramilitary groups that are joined together as allied forces in a given context.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 7:59 p.m.