Triple
T30036125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalkaska sand |
E763162
|
entity |
| Predicate | drainageClass |
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: [Kalkaska sand, drainageClass, well drained]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageClass Context triple: [Kalkaska sand, drainageClass, well drained]
-
A.
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).
-
B.
drainageBetween
Indicates that one area or feature serves as a drainage path or channel between two other areas or features, allowing water or runoff to flow from one to the other.
-
C.
hasDrainage
Indicates that one entity serves as the drainage system or outlet through which another entity’s liquid or runoff is removed or discharged.
-
D.
drainageRole
Indicates the functional role an entity plays in a drainage system, such as directing, collecting, or removing water or other fluids.
-
E.
drainageAssociatedWith
Indicates that one entity has a drainage relationship or connection with another, such as sharing, affecting, or being linked through water or fluid drainage.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d44f2081908ffa58a7709907ba |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:51 p.m.