Triple
T32495715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echinus Geyser |
E830516
|
entity |
| Predicate | hasSurfaceDeposits |
P167953
|
FINISHED |
| Object | silica |
—
|
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: silica | Statement: [Echinus Geyser, hasSurfaceDeposits, silica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceDeposits Context triple: [Echinus Geyser, hasSurfaceDeposits, silica]
-
A.
surfaceDeposits
chosen
Indicates that one entity has material or residue present on the surface of another entity.
-
B.
hasSurfaceComposition
Indicates that one entity has a surface made up of, or characterized by, the material or composition specified by another entity.
-
C.
hasSurfaceUse
Indicates that something is used or intended to be used on a surface (e.g., applied to, covering, or interacting with a surface).
-
D.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
E.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 12:59 a.m.