Triple
T19318329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taft family |
E483155
|
entity |
| Predicate | hasProminentGeneration |
P5987
|
FINISHED |
| Object | William Howard Taft generation |
—
|
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: William Howard Taft generation | Statement: [Taft family, hasProminentGeneration, William Howard Taft generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentGeneration Context triple: [Taft family, hasProminentGeneration, William Howard Taft generation]
-
A.
hasGenerations
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
B.
hasSecondGenerationLeader
Indicates that an entity is led or governed by a leader belonging to its second generation of leadership.
-
C.
hasTypeOfGeneration
Indicates that one entity is characterized by or associated with a particular kind or method of generation.
-
D.
dominantGeneration
chosen
Indicates that one generation in a life cycle is more prominent, long-lived, or visually conspicuous than the other generation(s).
-
E.
notableGeneration
Indicates that an entity is particularly distinguished or recognized among a specific generation or cohort.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d868dd48190b1439a5f4ff58c48 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.