Triple
T26431840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZaSu Pitts |
E664530
|
entity |
| Predicate | nameInBirthRegister |
P80791
|
FINISHED |
| Object | Eliza Susan Pitts |
E664529
|
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: Eliza Susan Pitts | Statement: [ZaSu Pitts, nameInBirthRegister, Eliza Susan Pitts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInBirthRegister Context triple: [ZaSu Pitts, nameInBirthRegister, Eliza Susan Pitts]
-
A.
bearerBirthNameOf
chosen
Indicates that one entity is the birth name originally given to and borne by another entity.
-
B.
civilRegistrationPrefixExample
Indicates that there is an example of a standard prefix used in civil registration identifiers or records.
-
C.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
D.
originalNameGivenByMother
Indicates that the name in question is the original name assigned to an individual specifically by their mother.
-
E.
nameGivenByFather
Indicates that a father is the one who assigned or chose the given name for a particular person.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611bebb8481909d7be89946db38d1 |
completed | May 2, 2026, 3:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12130d17448190b22b78c7d0e63f31 |
completed | May 23, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:50 p.m.