Triple
T27513817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annual Passport |
E694490
|
entity |
| Predicate | grantsAccessType |
P66994
|
FINISHED |
| Object | unlimited 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: unlimited access | Statement: [Annual Passport, grantsAccessType, unlimited access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsAccessType Context triple: [Annual Passport, grantsAccessType, unlimited access]
-
A.
grantedRightsType
chosen
Indicates the specific category or nature of rights that have been granted in a given permission or authorization relationship.
-
B.
designationGrantsAccessTo
Indicates that holding a particular designation or role grants permission to access a specific resource or capability.
-
C.
granteeType
Indicates the classification or category of the entity that receives a grant or is granted a right, benefit, or permission.
-
D.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
E.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 1:17 p.m.