Triple
T20330319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stickney crater |
E492458
|
entity |
| Predicate | mayHaveCaused |
P12716
|
FINISHED |
| Object | global fracturing of Phobos |
—
|
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: global fracturing of Phobos | Statement: [Stickney crater, mayHaveCaused, global fracturing of Phobos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveCaused Context triple: [Stickney crater, mayHaveCaused, global fracturing of Phobos]
-
A.
mayResultIn
chosen
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
mayEntail
Indicates that one statement or condition can logically lead to or imply the truth of another, without guaranteeing it.
-
D.
mayAlsoOriginateFrom
Indicates that something has an additional possible source or origin beyond its primary or known one.
-
E.
debatedAsCauseOf
Indicates that one entity is discussed or argued over as a possible cause or origin of another entity.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e6f5d08190bedf376bbb999ebc |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:22 a.m.