Triple
T31143796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Hutchison |
E793863
|
entity |
| Predicate | nameIsRecordedAsBearerOfSurname |
P108409
|
FINISHED |
| Object | Hutchison |
—
|
NE NERFINISHED |
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: Hutchison | Statement: [William Hutchison, nameIsRecordedAsBearerOfSurname, Hutchison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameIsRecordedAsBearerOfSurname Context triple: [William Hutchison, nameIsRecordedAsBearerOfSurname, Hutchison]
-
A.
hasSurnameBearer
chosen
Indicates that a particular surname is borne or carried by a specific person or entity.
-
B.
isRecordedAsSurnameSinceCentury
Indicates that an entity has been documented or used as a surname starting from a specified century.
-
C.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
D.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
E.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 9:06 p.m.