Triple
T11258592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilanesberg Alkaline Ring Complex |
E266502
|
entity |
| Predicate | isVisibleOn |
P74583
|
FINISHED |
| Object | satellite imagery |
—
|
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: satellite imagery | Statement: [Pilanesberg Alkaline Ring Complex, isVisibleOn, satellite imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVisibleOn Context triple: [Pilanesberg Alkaline Ring Complex, isVisibleOn, satellite imagery]
-
A.
isVisibleAs
Indicates that one entity can be perceived or appears to observers under the form, name, or representation of another entity.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
isViewableIn
chosen
Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined by another entity.
-
D.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
E.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e936cb048190b4d6fb2851ef8932 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.