Triple
T5635299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowveld region |
E147931
|
entity |
| Predicate | typicalLandform |
P940
|
FINISHED |
| Object | low-lying plains |
—
|
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: low-lying plains | Statement: [Lowveld region, typicalLandform, low-lying plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLandform Context triple: [Lowveld region, typicalLandform, low-lying plains]
-
A.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
B.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
C.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
D.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
E.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0226286208190b6ccf036cc09fe82 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.