Triple
T826903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tynwald |
E17873
|
entity |
| Predicate | sessionFrequency |
P2557
|
FINISHED |
| Object | meets regularly throughout the year |
—
|
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: meets regularly throughout the year | Statement: [Tynwald, sessionFrequency, meets regularly throughout the year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionFrequency Context triple: [Tynwald, sessionFrequency, meets regularly throughout the year]
-
A.
sessionCount
Indicates the number of distinct sessions associated with an entity or interaction context.
-
B.
meetingFrequency
chosen
Indicates how often a meeting or recurring gathering takes place over a given period.
-
C.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
-
D.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
E.
hasCommunicationFrequency
Indicates how often communication occurs between the related entities.
- 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.