Triple
T27032456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veda |
E680956
|
entity |
| Predicate | hasMainLocale |
P195074
|
FINISHED |
| Object | Istanbul |
—
|
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: Istanbul | Statement: [Veda, hasMainLocale, Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLocale Context triple: [Veda, hasMainLocale, Istanbul]
-
A.
hasLocaleName
Indicates that an entity has a specific name or label used in a particular language or regional locale.
-
B.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
C.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
D.
hasPrimaryLanguageBranch
Indicates that an entity’s main or dominant language belongs to a specified language branch or family.
-
E.
hasPrimaryLanguageDialect
Indicates that an entity’s main or default language is a specific dialect of a broader language.
- F. None of above. chosen
Provenance (4 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 27, 2026, 7:14 a.m.