Triple
T9762272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamá Imelda |
E236697
|
entity |
| Predicate | enforcedTradition |
P34356
|
FINISHED |
| Object | ban on music |
—
|
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: ban on music | Statement: [Mamá Imelda, enforcedTradition, ban on music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcedTradition Context triple: [Mamá Imelda, enforcedTradition, ban on music]
-
A.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
D.
governedWithinTradition
chosen
Indicates that an entity’s actions, decisions, or organization are regulated or constrained according to a particular established tradition or customary framework.
-
E.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04c70108190a8ed09eb6f2a124e |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.