Triple
T10618222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharia |
E295177
|
entity |
| Predicate | hasTraditionalFolktales |
P32654
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kharia, hasTraditionalFolktales, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalFolktales Context triple: [Kharia, hasTraditionalFolktales, true]
-
A.
hasRichOralTradition
chosen
Indicates that an entity is associated with a longstanding, culturally significant body of stories, histories, or knowledge transmitted primarily through spoken word rather than written texts.
-
B.
basedOnOralTraditionsCollectedBy
Indicates that something is derived from or informed by oral traditions that were gathered or recorded by a specified collector or source.
-
C.
narrativeTradition
Indicates the storytelling customs, conventions, or patterns that shape how narratives are typically told within a particular culture, group, or context.
-
D.
hasTraditionalDialect
Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
-
E.
talesCount
Indicates the number of tales associated with or attributed to a given entity.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d6df6ee1848190a7d5fcd40b06cfe3 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:19 p.m.