Triple
T31056658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIR 2004 |
E791414
|
entity |
| Predicate | typeOfAccessRight |
P5038
|
FINISHED |
| Object | statutory right of access |
—
|
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: statutory right of access | Statement: [EIR 2004, typeOfAccessRight, statutory right of access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAccessRight Context triple: [EIR 2004, typeOfAccessRight, statutory right of access]
-
A.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
B.
typeOfRight
chosen
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
-
C.
accessRight
Indicates that one entity has a specified permission or level of authorization to use, view, or interact with another entity or resource.
-
D.
grantedRightsType
Indicates the specific category or nature of rights that have been granted in a given permission or authorization relationship.
-
E.
typeOfAuthorization
Indicates the specific kind or category of authorization that applies to an action, resource, or relationship between 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: April 29, 2026, 9 p.m.