Triple
T21026496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M88 |
E517953
|
entity |
| Predicate | HubbleSequenceType |
P140170
|
FINISHED |
| Object | Sb–Sc |
—
|
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: Sb–Sc | Statement: [M88, HubbleSequenceType, Sb–Sc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HubbleSequenceType Context triple: [M88, HubbleSequenceType, Sb–Sc]
-
A.
HubbleSequencePosition
chosen
Indicates the position of a galaxy along the Hubble sequence, specifying its morphological type within the classification scheme.
-
B.
sequencerType
Indicates the specific kind or category of sequencer associated with or used in relation to an entity.
-
C.
eraSequence
Indicates that one era or time period directly follows or precedes another in a chronological sequence.
-
D.
isHubbleDeploymentMission
Indicates that a mission involves deploying, servicing, or otherwise directly supporting the Hubble Space Telescope.
-
E.
sequencingMode
Indicates the specific order or pattern in which related items, events, or operations are arranged or executed.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7c262c8190bceb8fd26be76983 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.