Triple
T35894240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basil Patten |
E1038172
|
entity |
| Predicate | nameUsedAsNamesake |
P132742
|
FINISHED |
| Object | Patten surname-related entities |
—
|
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: Patten surname-related entities | Statement: [Basil Patten, nameUsedAsNamesake, Patten surname-related entities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsedAsNamesake Context triple: [Basil Patten, nameUsedAsNamesake, Patten surname-related entities]
-
A.
usedAsNamesakeFor
chosen
Indicates that one entity serves as the source or inspiration for the name given to another entity.
-
B.
usedAsFirstNameOf
Indicates that one entity functions as the given or first name of another entity.
-
C.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
D.
usesTheonym
Indicates that one entity refers to or designates another entity by using a theonym, i.e., the proper name of a deity.
-
E.
hasEarlierNamesake
Indicates that an entity shares its name with another entity that existed earlier in time.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3c136c8190805071af3eb852d6 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.