Triple
T9666382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelham-Holles |
E233714
|
entity |
| Predicate | namingPracticeType |
P2555
|
FINISHED |
| Object | aristocratic surname combination |
—
|
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: aristocratic surname combination | Statement: [Pelham-Holles, namingPracticeType, aristocratic surname combination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingPracticeType Context triple: [Pelham-Holles, namingPracticeType, aristocratic surname combination]
-
A.
namesakeType
Indicates the specific kind or category of namesake relationship that exists between two entities (for example, one being named after the other as a person, place, event, or object).
-
B.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
C.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
D.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
-
E.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3a63948190be3f48f87bdbccf1 |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.