Triple
T27341231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tollense River |
E690107
|
entity |
| Predicate | approximateBattleDate |
P185194
|
FINISHED |
| Object | circa 1300–1200 BCE |
—
|
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: circa 1300–1200 BCE | Statement: [Tollense River, approximateBattleDate, circa 1300–1200 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateBattleDate Context triple: [Tollense River, approximateBattleDate, circa 1300–1200 BCE]
-
A.
yearOfFirstBattle
Indicates the specific year in which the first battle involving the given entities took place.
-
B.
yearOfBattle
Indicates the specific calendar year in which a particular battle took place.
-
C.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
D.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
E.
battleEndYear
Indicates the calendar year in which a particular battle or military engagement concluded.
- F. None of above. chosen
Provenance (4 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: April 27, 2026, 11:43 a.m.