Triple
T33195884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prairie River |
E849756
|
entity |
| Predicate | typicalLandUseAround |
P19783
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Prairie River, typicalLandUseAround, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLandUseAround Context triple: [Prairie River, typicalLandUseAround, agriculture]
-
A.
surroundedByLandUse
Indicates that an area or feature is encircled or bordered on all sides by specified types of land use.
-
B.
hasNearbyLandUse
chosen
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
C.
landUseContext
Indicates the contextual setting or circumstances under which a particular piece of land is used or designated for a specific purpose.
-
D.
servesLandUseType
Indicates that one entity functions to support, accommodate, or provide services for a specified land use type.
-
E.
otherLandUse
Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.