Triple
T25593816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lake Peipus |
E641592
|
entity |
| Predicate | hasMainCommanderForTeutonicOrder |
P61055
|
FINISHED |
| Object | Hermann of Dorpat |
—
|
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: Hermann of Dorpat | Statement: [Battle of Lake Peipus, hasMainCommanderForTeutonicOrder, Hermann of Dorpat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCommanderForTeutonicOrder Context triple: [Battle of Lake Peipus, hasMainCommanderForTeutonicOrder, Hermann of Dorpat]
-
A.
partyRepresentingTeutonicOrder
Indicates that a party is acting on behalf of, or in the capacity of, the Teutonic Order in a given context.
-
B.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
C.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
D.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
E.
hasPrimaryCrusaderLeader
chosen
Indicates that an entity (such as a crusade or crusading force) is associated with a specific individual who serves as its main or principal crusader leader.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 21, 2026, 4:26 p.m.