Triple
T20403750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble V |
E500405
|
entity |
| Predicate | catalogDesignation |
P974
|
FINISHED |
| Object | Hubble V |
—
|
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: Hubble V | Statement: [Hubble V, catalogDesignation, Hubble V]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hubble V Context triple: [Hubble V, catalogDesignation, Hubble V]
-
A.
Hubble V
chosen
Hubble V is a massive, bright star-forming nebula in the Triangulum Galaxy, notable as one of the largest known H II regions in the Local Group.
-
B.
Hubble Y
Hubble Y is a small satellite impact crater on the Moon located near the larger Hubble crater on the lunar far side.
-
C.
Hubble B
Hubble B is a small satellite impact crater on the Moon located near the larger Hubble crater on the lunar far side.
-
D.
Hubble G
Hubble G is a small satellite impact crater on the Moon located near the larger Hubble crater on the lunar far side.
-
E.
Hubble Z
Hubble Z is a small satellite impact crater on the Moon located near the larger Hubble crater on the lunar far side.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6799080cc819096dc31f41d1d7b49 |
completed | April 20, 2026, 7:08 p.m. |
Created at: April 16, 2026, 11:29 a.m.