Triple
T20479438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinalia Faculae |
E502411
|
entity |
| Predicate | surfaceProcessEvidenceFor |
P3650
|
FINISHED |
| Object | recent brine effusion |
—
|
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: recent brine effusion | Statement: [Vinalia Faculae, surfaceProcessEvidenceFor, recent brine effusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceProcessEvidenceFor Context triple: [Vinalia Faculae, surfaceProcessEvidenceFor, recent brine effusion]
-
A.
hasProcessEvidence
Indicates that there is supporting evidence for a process or procedure associated with the subject in relation to the object.
-
B.
providesEvidenceFor
chosen
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
hasMaterialEvidence
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
-
D.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
E.
evidenceOfProtection
Indicates that something serves as proof or indication that protection or safeguarding is present or has occurred.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b55d7a881909dfe3ea0e74b742b |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.