Triple
T33353612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lech |
E854009
|
entity |
| Predicate | influencedBattle |
P117285
|
FINISHED |
| Object | Battle of Lechfeld (955) |
—
|
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 Lechfeld (955) | Statement: [Lech, influencedBattle, Battle of Lechfeld (955)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedBattle Context triple: [Lech, influencedBattle, Battle of Lechfeld (955)]
-
A.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
B.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
C.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
battleRelatedTo
chosen
Indicates a relationship where one entity is connected to, associated with, or relevant to a particular battle or combat event.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 1:34 a.m.