Triple
T7329115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willakenzie soil |
E168952
|
entity |
| Predicate | hasDrainageClass |
P36221
|
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: [Willakenzie soil, hasDrainageClass, well-drained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrainageClass Context triple: [Willakenzie soil, hasDrainageClass, well-drained]
-
A.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
B.
drainageStatus
chosen
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
C.
drainagePattern
Indicates the characteristic spatial arrangement and connectivity of natural or artificial drainage features (such as streams, channels, or pipes) within an area.
-
D.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
-
E.
drainageRole
Indicates the functional role an entity plays in a drainage system, such as directing, collecting, or removing water or other fluids.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a9c0f081909218560d8a4f4995 |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.