Triple
T21071273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4388 |
E519111
|
entity |
| Predicate | showsHAlphaFilaments |
P142733
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NGC 4388, showsHAlphaFilaments, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsHAlphaFilaments Context triple: [NGC 4388, showsHAlphaFilaments, true]
-
A.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
B.
dominantEmissionLines
Indicates that the specified emission lines are the most intense or prominent spectral features in the observed emission from an object or region.
-
C.
hasSpectralLines
Indicates that one entity exhibits or is characterized by specific spectral lines associated with another entity.
-
D.
blueFireVisibleAt
Indicates that a blue fire is observable or can be seen at a specific location or point in time.
-
E.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:46 p.m.