Triple
T36610267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikyátki Revival style |
E903446
|
entity |
| Predicate | revivesTraditionsFrom |
P182856
|
FINISHED |
| Object | Sikyátki village |
—
|
NE NERFINISHED |
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: Sikyátki village | Statement: [Sikyátki Revival style, revivesTraditionsFrom, Sikyátki village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivesTraditionsFrom Context triple: [Sikyátki Revival style, revivesTraditionsFrom, Sikyátki village]
-
A.
consolidatesTraditionsFrom
Indicates that one entity combines, integrates, or unifies traditions originating from another entity.
-
B.
citesTradition
Indicates that one entity references, appeals to, or draws authority from a tradition associated with another entity.
-
C.
traditionsMaintainedBy
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
-
D.
usesTradition
chosen
Indicates that one entity employs or draws upon a tradition as a guiding method, resource, or influence in its actions or practices.
-
E.
traditionMergedInto
Indicates that one tradition has been absorbed into, combined with, or continued within another tradition, ceasing to exist as a separate 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.