Triple
T34569459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knipperlé |
E887583
|
entity |
| Predicate | believedToBeDescendantOf |
P66151
|
FINISHED |
| Object | Heunisch |
—
|
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: Heunisch | Statement: [Knipperlé, believedToBeDescendantOf, Heunisch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToBeDescendantOf Context triple: [Knipperlé, believedToBeDescendantOf, Heunisch]
-
A.
allegedAncestor
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
B.
spouseOfDescendantOf
Indicates that one entity is the spouse of a person who is a descendant of another entity.
-
C.
claimedDescentFrom
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
D.
possibleDescendant
chosen
Indicates that one entity may be a descendant of another, without asserting that the descendant relationship is certain.
-
E.
famousDescendant
Indicates that one entity is a descendant of another and is notable or widely recognized for some reason.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72092ea788190987ab862d8f10d95 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.