Triple
T38304399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Kępno |
E1032307
|
entity |
| Predicate | heirRecognizedBy |
P100751
|
FINISHED |
| Object | Mestwin 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: Mestwin II | Statement: [Treaty of Kępno, heirRecognizedBy, Mestwin II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heirRecognizedBy Context triple: [Treaty of Kępno, heirRecognizedBy, Mestwin II]
-
A.
madeHeirBy
chosen
Indicates that one entity is designated or appointed as the heir of another entity.
-
B.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
C.
grantedToHeirApparentOf
Indicates that something (such as a right, title, or privilege) is granted to the person who is the heir apparent of another individual.
-
D.
recognizedAsSuccessorToThrone
Indicates that one entity has been formally acknowledged or designated as the heir or next in line to inherit a throne from another entity.
-
E.
heirApparentOf
Indicates that one entity is the officially recognized primary successor who is expected to inherit a title, position, or role from another entity.
- 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_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.