Triple
T37097153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vhavenda |
E918592
|
entity |
| Predicate | culturalSignificanceOfLakeFundudzi |
P64908
|
FINISHED |
| Object | sacred lake |
—
|
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: sacred lake | Statement: [Vhavenda, culturalSignificanceOfLakeFundudzi, sacred lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalSignificanceOfLakeFundudzi Context triple: [Vhavenda, culturalSignificanceOfLakeFundudzi, sacred lake]
-
A.
hasLakeOrKund
Indicates that an entity possesses, contains, or is associated with a lake or kund (a water reservoir or pond).
-
B.
isHighAltitudeLake
Indicates that a lake is situated at a relatively high elevation above sea level.
-
C.
consideredAncientLake
Indicates that a body of water is regarded as an ancient lake, typically having existed continuously for a very long geological timespan.
-
D.
hasLakeThatRepresents
chosen
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
-
E.
locatedInFormerLake
Indicates that an entity is situated within the area that was once occupied by a lake that no longer exists.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.