Triple
T36121536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Olsnensis |
E1044754
|
entity |
| Predicate | usedInSeals |
P25490
|
FINISHED |
| Object | seals of the dukes of Oleśnica |
—
|
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: seals of the dukes of Oleśnica | Statement: [dux Olsnensis, usedInSeals, seals of the dukes of Oleśnica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSeals Context triple: [dux Olsnensis, usedInSeals, seals of the dukes of Oleśnica]
-
A.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
B.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
C.
isSealOf
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
D.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
firstSealAssociatedWith
Indicates that an entity is the earliest or primary seal linked or connected to another entity.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:08 p.m.