Triple
T31569849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Honigfeld |
E805525
|
entity |
| Predicate | kingPresent |
P29910
|
FINISHED |
| Object | Gustavus Adolphus of Sweden |
—
|
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: Gustavus Adolphus of Sweden | Statement: [Battle of Honigfeld, kingPresent, Gustavus Adolphus of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingPresent Context triple: [Battle of Honigfeld, kingPresent, Gustavus Adolphus of Sweden]
-
A.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
B.
crownPresent
Indicates that a crown is currently present on or with the relevant entity.
-
C.
kingOfSwedenPresent
chosen
Indicates that the current reigning monarch of Sweden is present at a specified place, event, or context.
-
D.
keyRoyalMinister
Indicates that the subject serves as the primary or principal royal minister to the referenced monarch or royal authority.
-
E.
ממלכה
Indicates a relationship where an entity functions as or belongs to a kingdom, typically denoting political or territorial sovereignty under a monarch.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:19 p.m.