Triple
T34816433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | judicial branch of Guyana |
E1003647
|
entity |
| Predicate | mayDeclare |
P2944
|
FINISHED |
| Object | laws unconstitutional |
—
|
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: laws unconstitutional | Statement: [judicial branch of Guyana, mayDeclare, laws unconstitutional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDeclare Context triple: [judicial branch of Guyana, mayDeclare, laws unconstitutional]
-
A.
canDeclare
chosen
Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
-
B.
mayDefine
Indicates that one entity has the authority or capability to specify, establish, or determine the form, content, or rules of another entity.
-
C.
mayEnact
Indicates that an entity has the authority or permission to establish, implement, or put into effect a rule, policy, or action.
-
D.
mustDeclare
Indicates that one entity is required or obligated to formally state, disclose, or announce something to another entity or authority.
-
E.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab971548190a1e0a1e5ffd5b85d |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 4 p.m.