Triple
T10790254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Anhalt-Zerbst |
E254558
|
entity |
| Predicate | usedMercenaryTroops |
P55764
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Principality of Anhalt-Zerbst, usedMercenaryTroops, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMercenaryTroops Context triple: [Principality of Anhalt-Zerbst, usedMercenaryTroops, yes]
-
A.
usedAsMercenaries
chosen
Indicates that certain entities are employed or deployed to fight or perform military actions on behalf of another party, typically in exchange for payment rather than loyalty.
-
B.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
C.
hasSoldier
Indicates that one entity possesses, employs, or is associated with a soldier or group of soldiers.
-
D.
maintainedPrivateArmy
Indicates that an entity kept and controlled its own private military force, separate from official or public armed forces.
-
E.
usedInWar
Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f5b8248190a633dc44ae620a3a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.