Triple
T3165597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hood River Valley |
E66203
|
entity |
| Predicate | agriculturalSpecialization |
P1897
|
FINISHED |
| Object | tree fruit |
—
|
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: tree fruit | Statement: [Hood River Valley, agriculturalSpecialization, tree fruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agriculturalSpecialization Context triple: [Hood River Valley, agriculturalSpecialization, tree fruit]
-
A.
agriculturalPractice
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
B.
farmingCharacteristics
Indicates the specific methods, practices, or attributes that characterize how farming is conducted in relation to an entity.
-
C.
majorCrop
chosen
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
D.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
E.
hasAgriculturalProduction
Indicates that an entity engages in or is characterized by the production of agricultural goods such as crops or livestock.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6424ee48190a29891ffbbc3811d |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.