Triple
T34569505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peurion |
E887584
|
entity |
| Predicate | geneticLineage |
P36142
|
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: [Peurion, geneticLineage, Heunisch Weiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticLineage Context triple: [Peurion, geneticLineage, Heunisch Weiss]
-
A.
genealogicalLine
chosen
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
B.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
C.
sharesFamilyLineageWith
Indicates that two entities descend from the same family line or share common ancestors.
-
D.
ancestralLinks
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
-
E.
hasGenealogy
Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of 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_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.