Triple
T21301894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4639 |
E525085
|
entity |
| Predicate | hasHubbleStage |
P143656
|
FINISHED |
| Object | bc |
—
|
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: bc | Statement: [NGC 4639, hasHubbleStage, bc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHubbleStage Context triple: [NGC 4639, hasHubbleStage, bc]
-
A.
isHubbleDeploymentMission
Indicates that a mission involves deploying, servicing, or otherwise directly supporting the Hubble Space Telescope.
-
B.
hasStageVersion
Indicates that one entity is a specific stage, phase, or version within the lifecycle or progression of another entity.
-
C.
hasHubbleFlowDistance
Indicates that a distance value is specified for an object as derived from the Hubble flow (cosmological expansion), rather than from local or non-cosmological distance measures.
-
D.
hasStageStructure
Indicates that one entity possesses or is characterized by a particular stage-based structural organization defined by another entity.
-
E.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385cd6308190bf300494833b048f |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:05 p.m.