Triple
T33090056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy Prescott Jr. |
E846753
|
entity |
| Predicate | hasLastNameSuffix |
P89620
|
FINISHED |
| Object | Jr. |
—
|
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: Jr. | Statement: [Rudy Prescott Jr., hasLastNameSuffix, Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLastNameSuffix Context triple: [Rudy Prescott Jr., hasLastNameSuffix, Jr.]
-
A.
familyNameSuffix
chosen
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
-
B.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
C.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
-
D.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
E.
nameEnding
Indicates that one entity’s name ends with the string or substring represented by the other entity.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:26 a.m.