Triple
T35727497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Glogoviensis |
E1032655
|
entity |
| Predicate | partOfTitleTradition |
P29673
|
FINISHED |
| Object | Piast ducal titulature |
—
|
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: Piast ducal titulature | Statement: [dux Glogoviensis, partOfTitleTradition, Piast ducal titulature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfTitleTradition Context triple: [dux Glogoviensis, partOfTitleTradition, Piast ducal titulature]
-
A.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
B.
textBelongsToTradition
Indicates that a given text is associated with, derived from, or recognized as part of a particular intellectual, cultural, or religious tradition.
-
C.
traditionIncludes
chosen
Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
-
D.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
E.
citesTradition
Indicates that one entity references, appeals to, or draws authority from a tradition associated with 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.