Triple
T35825393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Legnicensis |
E1035627
|
entity |
| Predicate | heldByDynastyBranch |
P26559
|
FINISHED |
| Object | Silesian Piasts |
—
|
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: Silesian Piasts | Statement: [Dux Legnicensis, heldByDynastyBranch, Silesian Piasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByDynastyBranch Context triple: [Dux Legnicensis, heldByDynastyBranch, Silesian Piasts]
-
A.
heldUnderDynasty
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
B.
dynasticBranch
Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
-
C.
heldByFamilyBranch
chosen
Indicates that something is possessed, controlled, or maintained by a specific branch or sub-lineage of a family.
-
D.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
E.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
- 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.