Triple
T14705251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Désirée |
E345412
|
entity |
| Predicate | ancestryStatus |
P45077
|
FINISHED |
| Object | unknown parentage |
—
|
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: unknown parentage | Statement: [Désirée, ancestryStatus, unknown parentage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestryStatus Context triple: [Désirée, ancestryStatus, unknown parentage]
-
A.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
B.
inheritanceStatus
Indicates the type or condition of inheritance rights or succession status that applies between related parties.
-
C.
genealogicalStatus
chosen
Indicates the familial or ancestral relationship that one individual has to another within a genealogy.
-
D.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
E.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb6086c608190a66c64e23a3e002f |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.