Triple
T38304398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Kępno |
E1032307
|
entity |
| Predicate | grantedHeirStatusTo |
P100751
|
FINISHED |
| Object | Przemysł II |
—
|
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: Przemysł II | Statement: [Treaty of Kępno, grantedHeirStatusTo, Przemysł II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedHeirStatusTo Context triple: [Treaty of Kępno, grantedHeirStatusTo, Przemysł II]
-
A.
grantedToHeirApparentOf
Indicates that something (such as a right, title, or privilege) is granted to the person who is the heir apparent of another individual.
-
B.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
C.
adoptedAsHeir
Indicates that one entity has been formally chosen and accepted as the legal heir or successor of another entity.
-
D.
madeHeirBy
chosen
Indicates that one entity is designated or appointed as the heir of another entity.
-
E.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 3, 2026, 4:30 p.m.