Triple
T7022068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African 2nd Division |
E162849
|
entity |
| Predicate | surrenderDateAtTobruk |
P4667
|
FINISHED |
| Object | 21 June 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: 21 June 1942 | Statement: [South African 2nd Division, surrenderDateAtTobruk, 21 June 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderDateAtTobruk Context triple: [South African 2nd Division, surrenderDateAtTobruk, 21 June 1942]
-
A.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
B.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
C.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
-
D.
placeOfSurrender
Indicates the location where an entity formally surrendered to another party.
-
E.
dateOfBritishEvacuation
Indicates the date on which British forces or authorities withdrew from or evacuated a specified place.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.