Triple
T20235943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 3918 |
E498147
|
entity |
| Predicate | excitationClass |
P111330
|
FINISHED |
| Object | high-excitation 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: high-excitation planetary nebula | Statement: [NGC 3918, excitationClass, high-excitation planetary nebula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excitationClass Context triple: [NGC 3918, excitationClass, high-excitation planetary nebula]
-
A.
excites
Indicates that one entity causes another entity to become excited, stimulated, or activated, typically by increasing its energy or arousal level.
-
B.
explosiveClass
Indicates the classification or category assigned to an explosive based on its type, properties, or regulatory class.
-
C.
clase
chosen
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
D.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
E.
exploresClass
Indicates that one entity actively investigates, studies, or examines a particular class or category of things.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716a5af0819095ea419a4d1f0d1d |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.