Triple
T38453944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Plains of Texas |
E912253
|
entity |
| Predicate | characteristicSoils |
P181064
|
FINISHED |
| Object | clay loams |
—
|
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: clay loams | Statement: [Rolling Plains of Texas, characteristicSoils, clay loams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicSoils Context triple: [Rolling Plains of Texas, characteristicSoils, clay loams]
-
A.
soilOrder
Indicates the classification relationship that assigns a soil entity to a specific soil order within a soil taxonomy system.
-
B.
soilDisposition
Indicates how soil is arranged, oriented, or distributed in relation to surrounding features or conditions.
-
C.
hasSoilTexture
chosen
Indicates that one entity (typically a soil or land area) possesses a specific soil texture classification (such as sandy, loamy, or clayey).
-
D.
soilPreference
Indicates the type or condition of soil that an entity prefers or is best suited to grow or exist in.
-
E.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: May 3, 2026, 4:31 p.m.