Triple
T30023953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5189 |
E762827
|
entity |
| Predicate | hasMorphologicalClass |
P60322
|
FINISHED |
| Object | bipolar planetary nebula |
—
|
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: bipolar planetary nebula | Statement: [NGC 5189, hasMorphologicalClass, bipolar planetary nebula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphologicalClass Context triple: [NGC 5189, hasMorphologicalClass, bipolar planetary nebula]
-
A.
morphologicalClass
chosen
Indicates the classification of an entity based on its morphological form or structural pattern.
-
B.
hasMorphologicalForm
Indicates that one entity is a specific morphological form or inflected variant of another entity.
-
C.
hasMorphosyntax
Indicates a relationship where an entity is associated with, characterized by, or analyzed in terms of its morphological and syntactic structure.
-
D.
hasMorphologicalPattern
Indicates that one entity exhibits or follows a specific morphological pattern defined or associated with another entity.
-
E.
hasMorphosyntacticBasis
Indicates that one linguistic element’s form or syntactic behavior is grounded in, derived from, or systematically determined by another element’s morphosyntactic properties.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 29, 2026, 6:48 p.m.