Triple
T1414721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tobruk (1942) |
E31886
|
entity |
| Predicate | capturedPersonnel |
P6764
|
FINISHED |
| Object | over 30,000 Allied troops |
—
|
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: over 30,000 Allied troops | Statement: [Battle of Tobruk (1942), capturedPersonnel, over 30,000 Allied troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedPersonnel Context triple: [Battle of Tobruk (1942), capturedPersonnel, over 30,000 Allied troops]
-
A.
carriedPrisonersFrom
Indicates that an entity transported prisoners away from a specified origin location or source.
-
B.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
C.
capturedCommander
Indicates that one party has taken a military commander from another party into custody or control.
-
D.
prisonersOfWar
chosen
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
-
E.
capturedEquipment
Indicates that one party has taken possession of another party’s equipment, typically as a result of conflict, competition, or enforcement.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e5f9d08190861206934cd71fd8 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.