Triple
T38468340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oder line defence |
E912636
|
entity |
| Predicate | majorBattles |
P15171
|
FINISHED |
| Object | Battle of the Seelow Heights |
—
|
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: Battle of the Seelow Heights | Statement: [Oder line defence, majorBattles, Battle of the Seelow Heights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBattles Context triple: [Oder line defence, majorBattles, Battle of the Seelow Heights]
-
A.
numberOfMajorBattles
Indicates the total count of significant or major battles associated with an entity or event.
-
B.
battleScale
Indicates the relative size or intensity of a battle, such as how large, extensive, or severe the conflict is.
-
C.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
-
D.
mainBattle
chosen
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
E.
hasTacticalBattles
Indicates that there are one or more specific tactical-level combat engagements occurring between the related entities.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:31 p.m.