Triple
T26296464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tvashtar Paterae |
E661431
|
entity |
| Predicate | ejectaMaterial |
P160558
|
FINISHED |
| Object | silicate pyroclasts |
—
|
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: silicate pyroclasts | Statement: [Tvashtar Paterae, ejectaMaterial, silicate pyroclasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejectaMaterial Context triple: [Tvashtar Paterae, ejectaMaterial, silicate pyroclasts]
-
A.
hasEjecta
Indicates that one entity produces or is associated with material expelled or thrown out from another entity as a result of an energetic event or process.
-
B.
ejectaExtent
Indicates the spatial reach or spread of material expelled from an impact or explosive event relative to its source.
-
C.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
D.
typicalEjectedMass
Indicates the characteristic amount of mass that is usually expelled from a system or object during an ejection event.
-
E.
ejectorType
Indicates the specific kind or category of ejector mechanism associated with an entity or system.
- F. None of above. chosen
Provenance (4 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eaea1d08190b93b85590b8c9781 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 10:12 p.m.