Triple
T26522342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2/22nd Battalion |
E669989
|
entity |
| Predicate | fateOfGarrison |
P106559
|
FINISHED |
| Object | overrun at Rabaul in 1942 |
—
|
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: overrun at Rabaul in 1942 | Statement: [2/22nd Battalion, fateOfGarrison, overrun at Rabaul in 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfGarrison Context triple: [2/22nd Battalion, fateOfGarrison, overrun at Rabaul in 1942]
-
A.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
B.
garrisonDestroyed
chosen
Indicates that a military garrison has been eliminated or rendered nonfunctional, typically through attack or destruction.
-
C.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
D.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
-
E.
garrisonAfterWar
Indicates that a military force is stationed in or occupies a location following the end of a war or major conflict.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c35b5481909ef85d87d1604be9 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:28 a.m.