Triple
T15140775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fundamental charter |
E361675
|
entity |
| Predicate | mayGuarantee |
P117481
|
FINISHED |
| Object | judicial independence |
—
|
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: judicial independence | Statement: [fundamental charter, mayGuarantee, judicial independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayGuarantee Context triple: [fundamental charter, mayGuarantee, judicial independence]
-
A.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
B.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
C.
seeksGuaranteesFor
Indicates that one entity actively pursues or requests assurances, protections, or commitments from another entity regarding a specific matter or outcome.
-
D.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
-
E.
guaranteeStatus
Indicates the current state or condition of a guarantee associated with an entity or agreement.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c46a248190a2364092d40274f3 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:07 a.m.