Triple
T651116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland-Lithuania in the early modern period |
E11346
|
entity |
| Predicate | hasNobilityClass |
P9679
|
FINISHED |
| Object | szlachta |
—
|
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: szlachta | Statement: [Poland-Lithuania in the early modern period, hasNobilityClass, szlachta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobilityClass Context triple: [Poland-Lithuania in the early modern period, hasNobilityClass, szlachta]
-
A.
nobilityClass
chosen
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
B.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
C.
hasPatronalTitle
Indicates that an entity holds or is associated with a specific patronal or honorific title, typically reflecting patronage, protection, or dedication.
-
D.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
E.
hasHeraldicFamily
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f33b6d881908b6662b73d6fe833 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.