Triple
T35825418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Legnicensis |
E1035627
|
entity |
| Predicate | overlordTitleLanguage |
P89513
|
FINISHED |
| Object | Latin titles of Polish rulers |
—
|
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: Latin titles of Polish rulers | Statement: [Dux Legnicensis, overlordTitleLanguage, Latin titles of Polish rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlordTitleLanguage Context triple: [Dux Legnicensis, overlordTitleLanguage, Latin titles of Polish rulers]
-
A.
titleOfOverlord
Indicates that one entity is the formal title or designation held by an overlord (a ruling or dominant authority) in relation to another entity.
-
B.
officialLanguageOfTitle
Indicates that a specified language is the officially designated language associated with a particular title or position.
-
C.
cultTitleLanguage
Indicates the language in which a cult title or religious honorific is expressed.
-
D.
throneNameLanguage
Indicates the language in which a ruler’s throne name or regnal title is expressed.
-
E.
titleInLanguage
chosen
Indicates that a specific title or name is expressed in a particular language.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.