Triple
T10071491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spruce Run Recreation Area |
E213638
|
entity |
| Predicate | hasWildlifeActivity |
P91941
|
FINISHED |
| Object | birdwatching |
—
|
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: birdwatching | Statement: [Spruce Run Recreation Area, hasWildlifeActivity, birdwatching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeActivity Context triple: [Spruce Run Recreation Area, hasWildlifeActivity, birdwatching]
-
A.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
-
B.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
C.
hasWildlifeAccess
Indicates that an entity has the ability, permission, or physical means to reach or interact with wildlife or wildlife habitats.
-
D.
hasWildlifeIssue
Indicates that an entity is affected by, involved in, or responsible for a problem or conflict related to wildlife.
-
E.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
- F. None of above. chosen
Provenance (4 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd01279388190b94c8def00425c78 |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:59 p.m.