Triple
T38151284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Freiberg |
E952757
|
entity |
| Predicate | commandingOfficerPrussia |
P17248
|
FINISHED |
| Object | Prince Henry of Prussia |
—
|
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: Prince Henry of Prussia | Statement: [Battle of Freiberg, commandingOfficerPrussia, Prince Henry of Prussia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandingOfficerPrussia Context triple: [Battle of Freiberg, commandingOfficerPrussia, Prince Henry of Prussia]
-
A.
PrussianCommander
chosen
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
B.
monarchOfPrussiaDuringWar
Indicates the person who held the position of monarch of Prussia during a specified war.
-
C.
associatedRulerTitlePrussia
Indicates a relationship where a ruler’s title is specifically linked to or held in connection with Prussia.
-
D.
commandStructurePrussia
Indicates the hierarchical command relationships within the Prussian military or administrative structure.
-
E.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:21 p.m.