Triple
T33212331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elysium Planitia |
E850192
|
entity |
| Predicate | hasSurfaceProcesses |
P67066
|
FINISHED |
| Object | volcanism |
—
|
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: volcanism | Statement: [Elysium Planitia, hasSurfaceProcesses, volcanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceProcesses Context triple: [Elysium Planitia, hasSurfaceProcesses, volcanism]
-
A.
hasSurfaceOperations
Indicates that an entity performs, supports, or is associated with activities or operations occurring on a surface.
-
B.
hasSurfaceActivity
chosen
Indicates that an entity exhibits measurable physical or chemical activity occurring at or on its surface.
-
C.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
D.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
E.
hasSurfaceUse
Indicates that something is used or intended to be used on a surface (e.g., applied to, covering, or interacting with a 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: May 1, 2026, 1:30 a.m.