Triple
T23074879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrymore family |
E575300
|
entity |
| Predicate | notableDynastyGeneration |
P150852
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Barrymore family, notableDynastyGeneration, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDynastyGeneration Context triple: [Barrymore family, notableDynastyGeneration, 19th century]
-
A.
notableGeneration
Indicates that an entity is particularly distinguished or recognized among a specific generation or cohort.
-
B.
notableDynastyEmergingFrom
Indicates that a notable or historically significant dynasty originated from or arose out of a specified source, such as a place, group, or earlier lineage.
-
C.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
D.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
E.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c62c200819099c92654493288ad |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:56 p.m.