Triple
T36765338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Näfels |
E908321
|
entity |
| Predicate | strengthHabsburg |
P186548
|
FINISHED |
| Object | several thousand men |
—
|
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: several thousand men | Statement: [Battle of Näfels, strengthHabsburg, several thousand men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthHabsburg Context triple: [Battle of Näfels, strengthHabsburg, several thousand men]
-
A.
strengthHabsburgCroatian
Indicates the degree or level of strength or influence present in the relationship between the Habsburg authority and Croatian entities.
-
B.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
C.
combatantStrengthHabsburg
Indicates the relative military strength or capability of a combatant in relation to the Habsburg side in a conflict.
-
D.
commandedByHabsburg
Indicates that the subject is under the military or political command or authority of a member or representative of the Habsburg dynasty.
-
E.
effectOnHabsburgs
Indicates the impact or consequences that something has on the Habsburgs as a group or dynasty.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.