Triple
T6076778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motsetse Cave |
E135419
|
entity |
| Predicate | hasScientificValue |
P68514
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Motsetse Cave, hasScientificValue, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientificValue Context triple: [Motsetse Cave, hasScientificValue, high]
-
A.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
B.
hasScientificStudy
Indicates that there exists a scientific study that investigates, analyzes, or provides evidence about the referenced entity or relationship.
-
C.
usesScientificInputFrom
Indicates that one entity bases its decisions, actions, or processes on scientific data, analysis, or expertise provided by another entity.
-
D.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
E.
hasCODATAValue
Indicates that an entity is associated with a value specified or standardized by CODATA (Committee on Data for Science and Technology).
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0576ef2c88190b0ec62e9f041d176 |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:11 p.m.