Triple
T13953314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Pond |
E335588
|
entity |
| Predicate | hasSurroundingLandCover |
P2022
|
FINISHED |
| Object | 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: forest | Statement: [Rocky Pond, hasSurroundingLandCover, forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingLandCover Context triple: [Rocky Pond, hasSurroundingLandCover, forest]
-
A.
hasLandCoverage
chosen
Indicates that a specified area or region is covered or occupied by a particular type of land surface or land use.
-
B.
hasNearbyLandscapeType
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
C.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
D.
forestCoverCharacteristic
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
-
E.
vegetationCoverage
Indicates the extent or proportion of an area that is covered by vegetation.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e146720819085d0f5eae558b7a4 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.