Triple
T31494768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumas Prairie |
E803504
|
entity |
| Predicate | formerLandCover |
P50021
|
FINISHED |
| Object | lake bed |
—
|
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: lake bed | Statement: [Sumas Prairie, formerLandCover, lake bed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLandCover Context triple: [Sumas Prairie, formerLandCover, lake bed]
-
A.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
-
B.
hasHistoricalLandCover
chosen
Indicates that an entity is associated with information about the land cover that existed in a specified area during a past time period.
-
C.
landUseChangeTo
Indicates a transition in how a piece of land is used, from its previous use to a new designated use.
-
D.
forestCoverCharacteristic
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
-
E.
landsPreviouslyBelongedTo
Indicates that the specified lands were owned, controlled, or possessed by a different party at an earlier time.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 30, 2026, 9:40 p.m.