Triple
T34041531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumark administration |
E872958
|
entity |
| Predicate | parentPolity |
P1815
|
FINISHED |
| Object | Holy Roman Empire |
—
|
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: Holy Roman Empire | Statement: [Neumark administration, parentPolity, Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentPolity Context triple: [Neumark administration, parentPolity, Holy Roman Empire]
-
A.
hasPolity
chosen
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
B.
politicalEntityPrecursorOf
Indicates that one political entity historically preceded and contributed to the formation, evolution, or establishment of another political entity.
-
C.
associatedPolityType
Indicates the type or category of political entity with which something is formally associated or linked.
-
D.
politicalEntityAtOrigin
Indicates that a political entity is located at, originates from, or has its primary base at a specified origin location.
-
E.
politicalEntity
Indicates that an entity functions as or is recognized as a political unit, organization, or actor within a political system.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:51 a.m.