Triple
T495334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurians |
E10279
|
entity |
| Predicate | folkloreType |
P11858
|
FINISHED |
| Object | Georgian oral tradition |
—
|
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: Georgian oral tradition | Statement: [Gurians, folkloreType, Georgian oral tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: folkloreType Context triple: [Gurians, folkloreType, Georgian oral tradition]
-
A.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
B.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
D.
narrativeType
chosen
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
E.
mythologicalEvent
Indicates an event or occurrence that takes place within mythological narratives or traditions, often involving gods, heroes, or supernatural phenomena.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0fdd5608190815fa36485df8962 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.