Triple
T38430717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnold von Winkelried |
E903790
|
entity |
| Predicate | roleInBattleOfSempach |
P204142
|
FINISHED |
| Object | created a breach in the Austrian pike line |
—
|
LITERAL FINISHED |
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: created a breach in the Austrian pike line | Statement: [Arnold von Winkelried, roleInBattleOfSempach, created a breach in the Austrian pike line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfSempach Context triple: [Arnold von Winkelried, roleInBattleOfSempach, created a breach in the Austrian pike line]
-
A.
roleInBattleOfLegnano
Indicates the specific role or involvement an entity had in the Battle of Legnano.
-
B.
roleInBattleOfGravelotte
Indicates the specific role or participation an entity had in the Battle of Gravelotte.
-
C.
sideInBattleOfWorringen
Indicates participation as a particular side or faction in the historical Battle of Worringen.
-
D.
sideInBattleOfCeresole
Indicates that an entity participated as a side or belligerent in the Battle of Ceresole.
-
E.
roleInBattleOfSanCarlos
Indicates the specific role or participation an entity had in the Battle of San Carlos.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0332a08b48819094aaed6e04a36886 |
completed | May 12, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_6a0331998a688190b5d919697d4231ac |
completed | May 12, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_6a03329fbbb0819099840a6a011eb411 |
completed | May 12, 2026, 2:01 p.m. |
Created at: May 3, 2026, 4:31 p.m.