Triple
T23648929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Shrovetide Football |
E584115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural tradition of England |
C26482
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: cultural tradition of England Context triple: [Royal Shrovetide Football, instanceOf, cultural tradition of England]
-
A.
English folk custom
chosen
An English folk custom is a traditional practice, ritual, or celebration rooted in the everyday life, beliefs, and seasonal cycles of communities in England, passed down through generations.
-
B.
Scottish tradition
Scottish tradition encompasses the customs, rituals, arts, and social practices rooted in Scotland’s history and cultural heritage, including music, dance, storytelling, festivals, and clan-based identities.
-
C.
tradition
Tradition is a collectively inherited pattern of beliefs, customs, and practices passed down through generations that shapes a group’s identity and behavior over time.
-
D.
Anglo-Saxon institution
An Anglo-Saxon institution is a social, legal, political, or economic structure characteristic of early medieval England and related Germanic societies, shaped by their customs, governance practices, and cultural norms.
-
E.
institution of the Kingdom of England
An institution of the Kingdom of England is an organized body or establishment, such as a legal, political, religious, or educational entity, that exercised authority or performed official functions within the English realm before its integration into the Kingdom of Great Britain.
- F. None of above.
Provenance (1 batch)
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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:49 p.m.