Triple
T29673271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Natural Area |
E750732
|
entity |
| Predicate | mayPermit |
P141119
|
FINISHED |
| Object | hiking on designated trails |
—
|
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: hiking on designated trails | Statement: [State Natural Area, mayPermit, hiking on designated trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayPermit Context triple: [State Natural Area, mayPermit, hiking on designated trails]
-
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.
mayAllowUse
chosen
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
C.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
D.
mayAdmit
Indicates that one entity has the permission or authority to allow another entity to enter, join, or be accepted into something.
-
E.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6725ac2d48190b0e65018d8294f94 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:06 p.m.