Triple
T24768169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helen Herron Taft |
E619641
|
entity |
| Predicate | birthNameIncludesSurname |
P110914
|
FINISHED |
| Object | Herron |
—
|
NE NERFINISHED |
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: Herron | Statement: [Helen Herron Taft, birthNameIncludesSurname, Herron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthNameIncludesSurname Context triple: [Helen Herron Taft, birthNameIncludesSurname, Herron]
-
A.
hasInitialOnlySurname
Indicates that a person is represented by only the initial of their given name together with their full surname, rather than their complete given name.
-
B.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
C.
isSurname
chosen
Indicates that one entity is the family name (last name) of another entity.
-
D.
memberHasCognomen
Indicates that a member is associated with or bears a specific cognomen (surname or additional family name).
-
E.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a8282c81909be28cbb83800ca0 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:28 a.m.