Triple
T11037469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godunov |
E260922
|
entity |
| Predicate | usedAsFamilyNameSinceCentury |
P23349
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Godunov, usedAsFamilyNameSinceCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFamilyNameSinceCentury Context triple: [Godunov, usedAsFamilyNameSinceCentury, 16th century]
-
A.
usedAsFirstNameSinceCentury
Indicates that an entity has been used as a first name starting from a specified century.
-
B.
usedAsSurname
chosen
Indicates that something functions as a family name borne by a person or group of people.
-
C.
associatedWithCenturyOfNameBearer
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
D.
usedAsBirthSurnameOf
Indicates that a particular surname served as the family name an individual was born with.
-
E.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fd5fe081908af13835b18de7b8 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.