Triple
T36121525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Olsnensis |
E1044754
|
entity |
| Predicate | usedForRulerOf |
P129715
|
FINISHED |
| Object | Oleśnica and surrounding lands |
—
|
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: Oleśnica and surrounding lands | Statement: [dux Olsnensis, usedForRulerOf, Oleśnica and surrounding lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForRulerOf Context triple: [dux Olsnensis, usedForRulerOf, Oleśnica and surrounding lands]
-
A.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
B.
usedForMonarchOf
chosen
Indicates that something serves as a means, tool, or context specifically for exercising the role or authority of a monarch.
-
C.
usedByRulersOf
Indicates that something is employed, utilized, or otherwise put to use by rulers or governing authorities.
-
D.
usedByRuler
Indicates that something is employed, utilized, or otherwise put to use by a ruler or governing authority.
-
E.
rulerDeity
Indicates that a deity holds supreme governing or sovereign authority over a realm, people, or cosmic domain.
- 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_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:08 p.m.