Triple
T31624606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathaniel Hubbard |
E806986
|
entity |
| Predicate | nameIsRecordedAsBearerOf |
P108409
|
FINISHED |
| Object | Hubbard 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: Hubbard surname | Statement: [Nathaniel Hubbard, nameIsRecordedAsBearerOf, Hubbard surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameIsRecordedAsBearerOf Context triple: [Nathaniel Hubbard, nameIsRecordedAsBearerOf, Hubbard surname]
-
A.
hasGivenNameOfBearer
Indicates that a bearer (such as a person or entity) has a specific given (first) name.
-
B.
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).
-
C.
hasSurnameBearer
chosen
Indicates that a particular surname is borne or carried by a specific person or entity.
-
D.
bearerPersonalName
Indicates that a personal name is borne or held by a particular entity (the bearer).
-
E.
bearerAnglicizedNameOf
Indicates that one entity is the anglicized (English-adapted) version of the name 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 10:42 p.m.