Triple
T569661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of the Legislature of Bermuda |
E13632
|
entity |
| Predicate | canBeChallengedOn |
P16122
|
FINISHED |
| Object | constitutional grounds |
—
|
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: constitutional grounds | Statement: [Acts of the Legislature of Bermuda, canBeChallengedOn, constitutional grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeChallengedOn Context triple: [Acts of the Legislature of Bermuda, canBeChallengedOn, constitutional grounds]
-
A.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
B.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
precedentChallenged
Indicates that an existing legal precedent is being questioned, disputed, or formally contested.
-
E.
canBeConvenedBy
Indicates that an entity (such as a group, body, or meeting) may be formally brought together or assembled by a specified agent or authority.
- F. None of above. chosen
Provenance (4 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b057e708190b4e5975516e58993 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498dd579081908e02368a4c5efc8c |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:33 p.m.