Triple
T36121535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Olsnensis |
E1044754
|
entity |
| Predicate | usedInCharters |
P198663
|
FINISHED |
| Object | ducal charters 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: ducal charters of Oleśnica | Statement: [dux Olsnensis, usedInCharters, ducal charters of Oleśnica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCharters Context triple: [dux Olsnensis, usedInCharters, ducal charters of Oleśnica]
-
A.
charteredIn
Indicates that an organization or entity has been formally established, authorized, or incorporated within a specified jurisdiction or location.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
chartersTo
Indicates that one entity formally grants another entity the right to use or operate something (such as a vehicle, vessel, or service) under a charter agreement.
-
D.
charterFeature
Indicates that an entity (such as a service, product, or offering) includes or provides a specific feature as part of a charter or special arrangement.
-
E.
usedInFlightPlansFor
Indicates that something (e.g., data, a procedure, or a resource) is employed as part of creating or executing flight plans for specific flights or routes.
- F. None of above. chosen
Provenance (4 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_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_69fefa05757481908fa38f5c604afbbe |
completed | May 9, 2026, 9:10 a.m. |
Created at: May 3, 2026, 4:08 p.m.