Triple
T31122314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magyar siege of Augsburg (955) |
E793255
|
entity |
| Predicate | defenceLedBy |
P154840
|
FINISHED |
| Object | Bishop Ulrich of Augsburg |
—
|
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: Bishop Ulrich of Augsburg | Statement: [Magyar siege of Augsburg (955), defenceLedBy, Bishop Ulrich of Augsburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenceLedBy Context triple: [Magyar siege of Augsburg (955), defenceLedBy, Bishop Ulrich of Augsburg]
-
A.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
B.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
-
C.
historicallyDefendedBy
Indicates that an entity has, in the past, received protection or military defense from another entity.
-
D.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
E.
townDefendedBy
chosen
Indicates that a particular town is protected or guarded by a specified defending force or entity.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 9:04 p.m.