Triple
T6362942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of Tynwald |
E143153
|
entity |
| Predicate | mayBeImplementedBy |
P8649
|
FINISHED |
| Object | secondary legislation |
—
|
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: secondary legislation | Statement: [Acts of Tynwald, mayBeImplementedBy, secondary legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeImplementedBy Context triple: [Acts of Tynwald, mayBeImplementedBy, secondary legislation]
-
A.
canBeImplementedWith
chosen
Indicates that one entity is capable of being realized, executed, or fulfilled through the use or application of another entity.
-
B.
fullyImplementedBy
Indicates that something (such as a specification, design, or requirement) is completely realized or carried out by a particular implementation or entity.
-
C.
isImplementationOf
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
-
D.
alsoImplements
Indicates that an entity, in addition to its primary implementation, implements another interface, protocol, or specification as well.
-
E.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680c02b481908618317566e31a5c |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.