Triple
T23580658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Smoky River |
E582191
|
entity |
| Predicate | hasNearbyLandCover |
P85343
|
FINISHED |
| Object | mixedwood forest |
—
|
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: mixedwood forest | Statement: [Little Smoky River, hasNearbyLandCover, mixedwood forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyLandCover Context triple: [Little Smoky River, hasNearbyLandCover, mixedwood forest]
-
A.
hasNearbyLandscapeType
chosen
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
B.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
C.
hasNearbyPublicLand
Indicates that one entity is located close to an area of public land, such as parks, reserves, or other publicly accessible open spaces.
-
D.
hasNearbyLandManager
Indicates that an entity has a land manager responsible for or operating on land located in close geographic proximity to it.
-
E.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02c265c819094728220d77172c6 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:39 p.m.