Triple
T28313437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dursun |
E714064
|
entity |
| Predicate | isGivenNameInOnomasticsCategory |
P99146
|
FINISHED |
| Object | Turkish masculine given names |
—
|
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: Turkish masculine given names | Statement: [Dursun, isGivenNameInOnomasticsCategory, Turkish masculine given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGivenNameInOnomasticsCategory Context triple: [Dursun, isGivenNameInOnomasticsCategory, Turkish masculine given names]
-
A.
isNameCategory
Indicates that something is classified as a particular category or type of name.
-
B.
isGivenName
Indicates that one entity is the personal (given) name of another entity.
-
C.
hasOnomasticField
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
D.
partOfOnomasticsCategory
Indicates that one concept or term belongs to, or is classified under, a specific category within the field of onomastics (the study of names).
-
E.
isGivenNameInCulture
chosen
Indicates that a particular given (first) name is used or recognized within a specified culture or cultural context.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e3dcb08190a8002133c931cc20 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:41 p.m.