Triple
T826908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tynwald |
E17873
|
entity |
| Predicate | TynwaldDayActivity |
P3473
|
FINISHED |
| Object | promulgation of laws on Tynwald Hill |
—
|
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: promulgation of laws on Tynwald Hill | Statement: [Tynwald, TynwaldDayActivity, promulgation of laws on Tynwald Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TynwaldDayActivity Context triple: [Tynwald, TynwaldDayActivity, promulgation of laws on Tynwald Hill]
-
A.
day1Event
Indicates that an event occurs on or is associated with the first day of a specified period or sequence.
-
B.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
-
C.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
D.
observesHolidayWithLocalCustoms
Indicates that an entity celebrates a holiday in a particular place following that location’s specific traditions and customs.
-
E.
celebratedDuring
chosen
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab989748819091a3809a747a1c5b |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.