Triple
T34853143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefanos crater |
E1004653
|
entity |
| Predicate | isMainCraterOf |
P95999
|
FINISHED |
| Object | Nisyros hydrothermal field |
—
|
NE NERFINISHED |
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: Nisyros hydrothermal field | Statement: [Stefanos crater, isMainCraterOf, Nisyros hydrothermal field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainCraterOf Context triple: [Stefanos crater, isMainCraterOf, Nisyros hydrothermal field]
-
A.
isSecondaryCraterOf
Indicates that one crater was formed by ejecta from the impact that created another, primary crater, rather than by a direct impact itself.
-
B.
mainCrater
chosen
Indicates that one crater is the primary or most significant crater associated with another crater or crater-related feature.
-
C.
isNamedCraterOn
Indicates that a crater bears a specific name and is located on a particular celestial body.
-
D.
dominantCraterName
Indicates that one crater is identified as the primary or most prominent (dominant) crater associated with another feature or context.
-
E.
largestCraterName
Indicates the name of the largest crater associated with a given celestial body or region.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.