Triple
T20838994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 1672 |
E513037
|
entity |
| Predicate | hasBulge |
P142040
|
FINISHED |
| Object | bright central bulge |
—
|
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: bright central bulge | Statement: [NGC 1672, hasBulge, bright central bulge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBulge Context triple: [NGC 1672, hasBulge, bright central bulge]
-
A.
bulge
Indicates that one entity protrudes outward or swells relative to another reference surface or boundary.
-
B.
hasBurgee
Indicates that an entity possesses or is associated with a specific burgee (a distinguishing flag, typically used by clubs or vessels).
-
C.
isCurved
Indicates that an object or path deviates smoothly from a straight line, forming a bend or arc.
-
D.
hasBore
Indicates that one object possesses or is characterized by a specific bore, such as the internal diameter of a tube, pipe, or barrel.
-
E.
hasCusp
Indicates that one entity possesses or exhibits a pointed or projecting feature (a cusp) as part of its form or structure.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c32928788190be8ca57923eefd7e |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:42 p.m.