Triple
T25175993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George D. Aiken Wilderness |
E630447
|
entity |
| Predicate | allowedRecreation |
P80228
|
FINISHED |
| Object | hunting |
—
|
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: hunting | Statement: [George D. Aiken Wilderness, allowedRecreation, hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedRecreation Context triple: [George D. Aiken Wilderness, allowedRecreation, hunting]
-
A.
supportsRecreationAt
chosen
Indicates that one entity provides facilities, conditions, or resources that enable recreational activities to take place at a specified location.
-
B.
canBeRecreated
Indicates that something has the potential to be created again or restored to a previous state.
-
C.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
D.
supportedCreationOf
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment of another entity.
-
E.
recreatedFor
Indicates that one entity has been created again or reproduced specifically for the benefit, use, or purpose of 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 12:34 p.m.