Triple
T4467304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antep baklavası |
E98408
|
entity |
| Predicate | isRegionalVariantOf |
P11942
|
FINISHED |
| Object | baklava |
—
|
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: baklava | Statement: [Antep baklavası, isRegionalVariantOf, baklava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalVariantOf Context triple: [Antep baklavası, isRegionalVariantOf, baklava]
-
A.
regionalVariantOf
chosen
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
B.
hasRegionalVariationsIn
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
E.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.