Triple
T26720508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khushal |
E673686
|
entity |
| Predicate | isCulturalOrigin |
P89586
|
FINISHED |
| Object | South Asian culture |
—
|
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: South Asian culture | Statement: [Khushal, isCulturalOrigin, South Asian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCulturalOrigin Context triple: [Khushal, isCulturalOrigin, South Asian culture]
-
A.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
-
B.
isCulturalDistinction
Indicates that one entity is recognized as a distinguishing cultural feature or marker in comparison to another entity or context.
-
C.
originatedInCulturalContext
chosen
Indicates that something began, developed, or was created within a particular cultural setting, tradition, or milieu.
-
D.
isPartOfCulturalDomain
Indicates that something belongs to, falls within, or is associated with a particular cultural sphere, tradition, or domain.
-
E.
isCulturalArea
Indicates that a given area is recognized or designated as a cultural region, characterized by shared cultural traits, practices, or heritage.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 3:40 a.m.