Triple
T20770950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Söğüt region |
E511228
|
entity |
| Predicate | presentDayLanguage |
P141452
|
FINISHED |
| Object | Turkish |
—
|
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 | Statement: [Söğüt region, presentDayLanguage, Turkish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayLanguage Context triple: [Söğüt region, presentDayLanguage, Turkish]
-
A.
presentDayNameLanguage
Indicates the language in which the present-day name of an entity is expressed.
-
B.
currentLanguageSituation
Indicates the language currently being used or in effect in a given context or situation.
-
C.
presentDayContext
Indicates that the relationship or action is situated in, or relevant to, the current time period or contemporary context.
-
D.
presentDayCityIs
Indicates that one entity is the current, modern-day city corresponding to or located at the place represented by the other entity.
-
E.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c266f4b48190891c0db3e322bb23 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:36 p.m.