Triple
T26580441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRDAP |
E667062
|
entity |
| Predicate | grantUseRestriction |
P9584
|
FINISHED |
| Object | projects must be for public outdoor recreation |
—
|
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: projects must be for public outdoor recreation | Statement: [FRDAP, grantUseRestriction, projects must be for public outdoor recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantUseRestriction Context triple: [FRDAP, grantUseRestriction, projects must be for public outdoor recreation]
-
A.
grantUse
Indicates that one entity gives another entity permission or authorization to use something.
-
B.
grantLocation
Indicates that an entity is located at, based in, or associated with a particular place or geographic location.
-
C.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
cannotRestrict
Indicates that one entity lacks the authority, ability, or right to impose limits, constraints, or prohibitions on another entity or its actions.
-
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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 2:02 a.m.