Triple
T20457084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5102 |
E501818
|
entity |
| Predicate | HubbleSequencePosition |
P140170
|
FINISHED |
| Object | early-type disk galaxy |
—
|
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: early-type disk galaxy | Statement: [NGC 5102, HubbleSequencePosition, early-type disk galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HubbleSequencePosition Context triple: [NGC 5102, HubbleSequencePosition, early-type disk galaxy]
-
A.
hasSequencePosition
Indicates that an element occupies a specific position or order within a sequence.
-
B.
orbiterSequenceNumber
Indicates the ordinal position assigned to an orbiter within a sequence of multiple orbiters associated with the same mission or system.
-
C.
isHubbleDeploymentMission
Indicates that a mission involves deploying, servicing, or otherwise directly supporting the Hubble Space Telescope.
-
D.
hasPartOfSeriesPosition
Indicates that an entity occupies a specific position or order within a larger series or sequence.
-
E.
HSTServicingNumber
Indicates the specific servicing mission number associated with work performed on the Hubble Space Telescope.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a1b03c8190984d9db6d3251308 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:32 a.m.