Triple
T15372946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seto language |
E367593
|
entity |
| Predicate | hasTraditionalGenre |
P60982
|
FINISHED |
| Object | leelo folk songs |
—
|
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: leelo folk songs | Statement: [Seto language, hasTraditionalGenre, leelo folk songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalGenre Context triple: [Seto language, hasTraditionalGenre, leelo folk songs]
-
A.
basedInGenreTradition
chosen
Indicates that something (such as a work or practice) is grounded in, follows, or is shaped by the conventions and traditions of a particular genre.
-
B.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
-
C.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
D.
hasCanonicalGenre
Indicates that an entity is associated with its primary or officially recognized genre classification.
-
E.
hasStageGenre
Indicates a relationship where a stage production or performance is associated with a particular theatrical or performance genre.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5c1d548190930bfaf0861595ae |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.