Triple
T20330344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stickney crater |
E492458
|
entity |
| Predicate | relatedToHypothesis |
P37
|
FINISHED |
| Object | Phobos may be a rubble pile or fractured body |
—
|
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: Phobos may be a rubble pile or fractured body | Statement: [Stickney crater, relatedToHypothesis, Phobos may be a rubble pile or fractured body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToHypothesis Context triple: [Stickney crater, relatedToHypothesis, Phobos may be a rubble pile or fractured body]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
C.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
-
D.
mayRelateTo
Indicates a possible, but not certain, relationship or association between two entities.
-
E.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference 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.