Triple
T30821023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Douglas-fir zone |
E784919
|
entity |
| Predicate | hasMoistureRegime |
P194188
|
FINISHED |
| Object | dry |
—
|
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: dry | Statement: [Coastal Douglas-fir zone, hasMoistureRegime, dry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoistureRegime Context triple: [Coastal Douglas-fir zone, hasMoistureRegime, dry]
-
A.
hasHydrologicalRegime
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
B.
hasIrrigationDependence
Indicates that one entity relies on another entity or system to provide irrigation for its water needs.
-
C.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
D.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
-
E.
hasSoilTexture
Indicates that one entity (typically a soil or land area) possesses a specific soil texture classification (such as sandy, loamy, or clayey).
- F. None of above. chosen
Provenance (4 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: April 29, 2026, 8:44 p.m.