Triple
T30991454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Bukovina |
E789678
|
entity |
| Predicate | hasAssociatedDuchy |
P80004
|
FINISHED |
| Object | Duchy of Bukovina |
—
|
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: Duchy of Bukovina | Statement: [Duke of Bukovina, hasAssociatedDuchy, Duchy of Bukovina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedDuchy Context triple: [Duke of Bukovina, hasAssociatedDuchy, Duchy of Bukovina]
-
A.
linkedToDuchy
chosen
Indicates a relationship where one entity is connected or associated with a specific duchy, such as by jurisdiction, governance, or territorial affiliation.
-
B.
wasDuchyWithin
Indicates that a political entity held the status of a duchy within the territorial or administrative boundaries of another entity.
-
C.
hasDominion
Indicates that one entity holds authority, control, or governing power over another entity or domain.
-
D.
oneOfOriginalStemDuchiesOf
Indicates that an entity was one of the original stem duchies from which the referenced political realm or kingdom historically emerged.
-
E.
associatedWithDynastyOrFaction
Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:56 p.m.