Triple
T9837385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bootle-Wilbraham |
E239136
|
entity |
| Predicate | hasFamilyNameType |
P49105
|
FINISHED |
| Object | toponymic surname |
—
|
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: toponymic surname | Statement: [Bootle-Wilbraham, hasFamilyNameType, toponymic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyNameType Context triple: [Bootle-Wilbraham, hasFamilyNameType, toponymic surname]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
hasFamilyNameOfOwner
Indicates that an entity has an owner whose family (last) name is the specified value.
-
C.
canBeFamilyName
Indicates that something is capable of functioning as a family name or surname in at least one context.
-
D.
hasSurnameType
chosen
Indicates that an entity’s surname belongs to a particular category or type (e.g., patronymic, toponymic, occupational).
-
E.
hasVariantFamilyName
Indicates that an entity is associated with an alternative or variant form of a family (last) name, differing from its primary recorded family name.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.