Triple
T3339919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Chalon-Arlay |
E70232
|
entity |
| Predicate | extinctionOfMaleLine |
P48008
|
FINISHED |
| Object | 16th century |
—
|
LITERAL FINISHED |
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: 16th century | Statement: [House of Chalon-Arlay, extinctionOfMaleLine, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionOfMaleLine Context triple: [House of Chalon-Arlay, extinctionOfMaleLine, 16th century]
-
A.
hadNoSurvivingChildren
Indicates that the person did not have any children who were alive at the relevant point in time.
-
B.
patriarchalLineage
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
C.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
D.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
E.
dynasticBranch
Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
- F. None of above. chosen
Provenance (4 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bf1f648190993ac8e9dda60983 |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69adaa518ac88190b64f949ace018ab7 |
completed | March 8, 2026, 4:56 p.m. |
Created at: March 8, 2026, 3:12 p.m.