Triple
T33820643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleszyce estates |
E866816
|
entity |
| Predicate | nobleTitleHeldByOwners |
P177737
|
FINISHED |
| Object | Polish magnates |
—
|
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: Polish magnates | Statement: [Oleszyce estates, nobleTitleHeldByOwners, Polish magnates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleTitleHeldByOwners Context triple: [Oleszyce estates, nobleTitleHeldByOwners, Polish magnates]
-
A.
aristocraticTitleHeldBy
Indicates that a specific aristocratic or noble title is held or borne by a particular person.
-
B.
nobleTitleHeldThrough
Indicates that an entity holds a noble title specifically by virtue of another person’s status, position, or relationship, rather than in their own independent right.
-
C.
aristocraticTitleHeldTo
Indicates that one entity holds or bears an aristocratic or noble title in relation to another entity (such as a person, family, or jurisdiction).
-
D.
nobleTitleHolderInPeriod
Indicates that a person held a specific noble title during a specified time period.
-
E.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
- F. None of above. chosen
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.