Triple
T25168373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork Eel River |
E630244
|
entity |
| Predicate | hasLandCoverAlong |
P2022
|
FINISHED |
| Object | coast redwood 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: coast redwood forest | Statement: [South Fork Eel River, hasLandCoverAlong, coast redwood forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandCoverAlong Context triple: [South Fork Eel River, hasLandCoverAlong, coast redwood 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.
hasHistoricalLandCover
Indicates that an entity is associated with information about the land cover that existed in a specified area during a past time period.
-
C.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
D.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
E.
isInLand
Indicates that one entity is located within the geographical boundaries of a land area or territory 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 21, 2026, 12:18 p.m.