Triple
T21920983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hale Z |
E541312
|
entity |
| Predicate | hasEponymType |
P146565
|
FINISHED |
| Object | letter designation of parent crater |
—
|
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: letter designation of parent crater | Statement: [Hale Z, hasEponymType, letter designation of parent crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymType Context triple: [Hale Z, hasEponymType, letter designation of parent crater]
-
A.
hasEponymConnectionTo
Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
-
B.
hasEponymField
Indicates that something (such as a concept, object, or entity) is named after a particular person or eponym.
-
C.
hasEponymFamilyRelation
Indicates that one entity is named after another entity to which it is related by family or kinship.
-
D.
isNamedForEponymRole
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
-
E.
hasEponymousLabel
Indicates that something is named after a particular person, place, or entity, serving as its eponym.
- F. None of above. chosen
Provenance (4 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233af5a481908072c7c928e065ad |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:45 p.m.