Triple
T31907827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Yarborough |
E814600
|
entity |
| Predicate | notableFamilySurname |
P149002
|
FINISHED |
| Object | Pelham |
E213726
|
NE 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: Pelham | Statement: [Baron Yarborough, notableFamilySurname, Pelham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilySurname Context triple: [Baron Yarborough, notableFamilySurname, Pelham]
-
A.
notableFamilyNameOf
chosen
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
B.
notableSurnameBranch
Indicates that a particular family branch is distinguished or noteworthy within a broader surname lineage.
-
C.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
D.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
E.
refersToNotableFamily
Indicates that an entity is associated with, or makes reference to, a specific well-known or historically significant family.
- F. None of above.
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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a30306c8190ad8200703c1e0c20 |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, midnight