Triple
T27341232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tollense River |
E690107
|
entity |
| Predicate | battlefieldLocatedIn |
P162197
|
FINISHED |
| Object | Tollense Valley |
—
|
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: Tollense Valley | Statement: [Tollense River, battlefieldLocatedIn, Tollense Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlefieldLocatedIn Context triple: [Tollense River, battlefieldLocatedIn, Tollense Valley]
-
A.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
B.
primaryBattlefieldOf
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
-
C.
battlefieldSector
Indicates a specific area or zone of a battlefield in which a military unit, action, or event is located or occurs.
-
D.
countryOfBattlefieldToday
Indicates the country in which the battlefield is located in the present day, regardless of its historical political status.
-
E.
nearbyBattlefield
Indicates that one entity is located close to or in the immediate vicinity of a battlefield.
- 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_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:43 a.m.