Triple
T15729244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Mashu |
E381297
|
entity |
| Predicate | visibilityRecord |
P74023
|
FINISHED |
| Object | underwater visibility exceeding 30 meters |
—
|
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: underwater visibility exceeding 30 meters | Statement: [Lake Mashu, visibilityRecord, underwater visibility exceeding 30 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityRecord Context triple: [Lake Mashu, visibilityRecord, underwater visibility exceeding 30 meters]
-
A.
visibilityCycle
Indicates a recurring pattern in which something alternates between being visible and not visible over time.
-
B.
visibilityStatus
chosen
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
C.
visibilityReason
Indicates the reason or cause for why something is visible or has become visible in a given context.
-
D.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
-
E.
visibleRemains
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb4cc0081909efe330339474017 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.