Triple
T23854142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarbell |
E592255
|
entity |
| Predicate | hasNotableMaleBearer |
P154205
|
FINISHED |
| Object | Edmund C. Tarbell |
—
|
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: Edmund C. Tarbell | Statement: [Tarbell, hasNotableMaleBearer, Edmund C. Tarbell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMaleBearer Context triple: [Tarbell, hasNotableMaleBearer, Edmund C. Tarbell]
-
A.
hasNotableSon
Indicates that an entity has a son who is recognized as notable or significant in some context.
-
B.
hasNotablePatriarch
Indicates that an entity is associated with a prominent or historically significant male ancestral or founding figure.
-
C.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
D.
lastLegitimateMaleHeirOf
Indicates that one entity is the final male descendant in a legitimate line of succession or inheritance from another entity.
-
E.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98954748190b39e0ac69e5625f9 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.