Triple
T32679357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich II. von Hessen-Kassel |
E835526
|
entity |
| Predicate | troopTypeProvided |
P6154
|
FINISHED |
| Object | Hessian auxiliaries |
—
|
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: Hessian auxiliaries | Statement: [Friedrich II. von Hessen-Kassel, troopTypeProvided, Hessian auxiliaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: troopTypeProvided Context triple: [Friedrich II. von Hessen-Kassel, troopTypeProvided, Hessian auxiliaries]
-
A.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
B.
troopAccess
Indicates that one party is permitted to move, station, or operate military troops within the territory, facilities, or jurisdiction of another party.
-
C.
garrisonOrCrewType
Indicates the specific kind of garrison or crew assigned to occupy, staff, or operate a given entity.
-
D.
hasBattalionType
Indicates that an entity (such as a military unit) is associated with or classified by a specific type of battalion.
-
E.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e7956c8190a3f54d6d6ff803f1 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.