Triple
T31645166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dudukugala |
E807565
|
entity |
| Predicate | originalTradition |
P202990
|
FINISHED |
| Object | oral transmission |
—
|
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: oral transmission | Statement: [Dudukugala, originalTradition, oral transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTradition Context triple: [Dudukugala, originalTradition, oral transmission]
-
A.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
B.
modernTradition
Indicates a relationship where a practice or custom is recognized as a contemporary development that functions like a tradition within a culture or group.
-
C.
usesTradition
Indicates that one entity employs or draws upon a tradition as a guiding method, resource, or influence in its actions or practices.
-
D.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
E.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00d8ba18808190976682088a02a9a8 |
completed | May 10, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a00d85fad64819084f424ec8ecd3b57 |
completed | May 10, 2026, 7:11 p.m. |
| PDg | Predicate description generation | batch_6a00d8b8eac08190809c78998e09c47c |
completed | May 10, 2026, 7:12 p.m. |
Created at: April 30, 2026, 10:50 p.m.