Triple
T34690130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genouillet |
E890868
|
entity |
| Predicate | believedToDescendFrom |
P30356
|
FINISHED |
| Object | Heunisch Weiss |
—
|
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 Weiss | Statement: [Genouillet, believedToDescendFrom, Heunisch Weiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToDescendFrom Context triple: [Genouillet, believedToDescendFrom, Heunisch Weiss]
-
A.
claimedDescentFrom
chosen
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
B.
ofDescent
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
C.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
D.
allegedAncestor
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
E.
hasTypeOfDescent
Indicates that one entity possesses a particular kind or category of ancestral or lineage-based origin in relation to 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72350dd7881908a30f0e2e230931c |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.