Triple
T18491812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whites |
E451835
|
entity |
| Predicate | hasTypicalAncestry |
P26561
|
FINISHED |
| Object | European ancestry |
—
|
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: European ancestry | Statement: [Whites, hasTypicalAncestry, European ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAncestry Context triple: [Whites, hasTypicalAncestry, European ancestry]
-
A.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
B.
typeOfAncestry
Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
-
C.
typicalAncestryDescription
chosen
Indicates the usual or most common ancestral background associated with an entity.
-
D.
ancestralStatus
Indicates that one entity holds a particular ancestral or lineage-based relationship or status in relation to another entity.
-
E.
hasAncestralType
Indicates that one type is derived from, or originates from, another more primitive or original type in an inheritance or lineage hierarchy.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531dcac3c8190b2ebd129ca7f368d |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.