Triple
T20773107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kopaida |
E511284
|
entity |
| Predicate | regionTypeAfterDrainage |
P1828
|
FINISHED |
| Object | agricultural plain |
—
|
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: agricultural plain | Statement: [Kopaida, regionTypeAfterDrainage, agricultural plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypeAfterDrainage Context triple: [Kopaida, regionTypeAfterDrainage, agricultural plain]
-
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.
regionDrained
Indicates that one region serves as the drainage area for another, collecting and channeling its surface or groundwater flow.
-
C.
regionType
chosen
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
D.
drainageStatus
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
E.
drainsAreaOf
Indicates that one entity serves as a drainage outlet or basin for another entity, carrying away its surface or groundwater.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c269638881909d96b847f7de5585 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.