Triple
T1412701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witwatersrand |
E31839
|
entity |
| Predicate | isRidge |
P26647
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Witwatersrand, isRidge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRidge Context triple: [Witwatersrand, isRidge, yes]
-
A.
ridgeType
Indicates the specific morphological or structural category that a ridge belongs to within a classification of ridge forms.
-
B.
slopeType
Indicates the classification of a slope based on its geometric or physical characteristics, such as steepness, shape, or orientation.
-
C.
isIsotropic
Indicates that a property or behavior is identical in all directions, showing no directional dependence.
-
D.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
E.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other entity.
- F. None of above. chosen
Provenance (4 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e3383c81909acb9c6c1c3b817a |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf048b648190ab77d9b45cb4855f |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:59 p.m.