Triple
T26296465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tvashtar Paterae |
E661431
|
entity |
| Predicate | ejectaMaterial |
P160558
|
FINISHED |
| Object | dust and gas |
—
|
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: dust and gas | Statement: [Tvashtar Paterae, ejectaMaterial, dust and gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejectaMaterial Context triple: [Tvashtar Paterae, ejectaMaterial, dust and gas]
-
A.
ejectaMaterial
chosen
Indicates that one entity consists of or represents material that has been expelled or thrown out from another entity, typically by an energetic event such as an impact or explosion.
-
B.
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.
-
C.
ejectaExtent
Indicates the spatial reach or spread of material expelled from an impact or explosive event relative to its source.
-
D.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
E.
typicalEjectedMass
Indicates the characteristic amount of mass that is usually expelled from a system or object during an ejection event.
- 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_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_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:12 p.m.