Triple
T17389504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escanaba River |
E422778
|
entity |
| Predicate | basinLandCover |
P116511
|
FINISHED |
| Object | predominantly forested |
—
|
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: predominantly forested | Statement: [Escanaba River, basinLandCover, predominantly forested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basinLandCover Context triple: [Escanaba River, basinLandCover, predominantly forested]
-
A.
drainageBasinLandCover
chosen
Indicates the type or characteristics of land cover present within a drainage basin area.
-
B.
drainageBasinLandUse
Indicates how the land within a drainage basin is utilized or managed (e.g., for agriculture, urban development, or natural vegetation).
-
C.
basinFeature
Indicates that one entity is a physical feature or component located within or forming part of a basin.
-
D.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
E.
forestCoverCharacteristic
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8c718c81909cb20749aaf12897 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.