Triple
T34698283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Palace Hill |
E891091
|
entity |
| Predicate | primaryAccessPurpose |
—
|
GENERATED |
| Object | visiting the Imperial Palace of Goslar |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAccessPurpose Context triple: [Imperial Palace Hill, primaryAccessPurpose, visiting the Imperial Palace of Goslar]
-
A.
accessPurpose
chosen
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
B.
secretPurpose
Indicates that an entity has an underlying goal, intention, or function that is deliberately concealed or not openly disclosed.
-
C.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
D.
primaryManagementPurpose
Indicates the main managerial objective or reason for which something (such as an organization, project, or resource) is overseen or directed.
-
E.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
- F. None of above.
Provenance (1 batch)
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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.