Triple
T1474779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas Peak AVA |
E30812
|
entity |
| Predicate | soilDrainage |
P3833
|
FINISHED |
| Object | well-drained |
—
|
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: well-drained | Statement: [Atlas Peak AVA, soilDrainage, well-drained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soilDrainage Context triple: [Atlas Peak AVA, soilDrainage, well-drained]
-
A.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
B.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
C.
drainageType
chosen
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
D.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
-
E.
droughtTolerance
Indicates the degree to which an entity can maintain normal function and survival under conditions of limited water availability.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6011d248190988380eca4ecf514 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.