Triple
T24248875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herschel crater |
E603456
|
entity |
| Predicate | givesAppearance |
P143336
|
FINISHED |
| Object | Death Star-like appearance to Mimas |
—
|
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: Death Star-like appearance to Mimas | Statement: [Herschel crater, givesAppearance, Death Star-like appearance to Mimas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesAppearance Context triple: [Herschel crater, givesAppearance, Death Star-like appearance to Mimas]
-
A.
publicAppearance
Indicates that an entity participates in or is present at an event or situation that is open or visible to the general public.
-
B.
describesAppearanceOf
chosen
Indicates that one entity provides information about the visual characteristics or outward look of another entity.
-
C.
coreAppearance
Indicates that one entity serves as the primary or defining visual form or look of another entity.
-
D.
hasCharacterAppearance
Indicates that a character appears or is visually represented within a given work, scene, or context.
-
E.
returnAppearance
Indicates that one entity resumes or restores a previous visual form, style, or outward appearance of another entity or of itself.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b87d03c8190a38ca0c0b65ce6fc |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.