Triple
T5774813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hale crater |
E127412
|
entity |
| Predicate | hasEjectaType |
P49676
|
FINISHED |
| Object | fluidized ejecta |
—
|
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: fluidized ejecta | Statement: [Hale crater, hasEjectaType, fluidized ejecta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEjectaType Context triple: [Hale crater, hasEjectaType, fluidized ejecta]
-
A.
hasEjecta
chosen
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.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
-
C.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
D.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
E.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.