Triple
T25336089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub Dome |
E635281
|
entity |
| Predicate | permitContext |
P129091
|
FINISHED |
| Object | Half Dome day-use permit system |
—
|
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: Half Dome day-use permit system | Statement: [Sub Dome, permitContext, Half Dome day-use permit system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitContext Context triple: [Sub Dome, permitContext, Half Dome day-use permit system]
-
A.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
B.
accessContext
chosen
Indicates the contextual conditions (such as environment, permissions, or circumstances) under which access to a resource or action is allowed or occurs.
-
C.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
-
D.
requiresPermitFrom
Indicates that one entity must obtain formal permission or authorization from another entity before proceeding with an action or process.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497ca0f18819090168e3221c2aa32 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.