Triple
T21294669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4569 |
E524888
|
entity |
| Predicate | hasBulgeType |
P143626
|
FINISHED |
| Object | prominent 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: prominent bulge | Statement: [NGC 4569, hasBulgeType, prominent bulge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBulgeType Context triple: [NGC 4569, hasBulgeType, prominent bulge]
-
A.
hasBulge
Indicates that one entity possesses or exhibits a protruding or swollen part relative to its surrounding surface or structure.
-
B.
bulge
Indicates that one entity protrudes outward or swells relative to another reference surface or boundary.
-
C.
hasBoreType
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
D.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
E.
hasBurgee
Indicates that an entity possesses or is associated with a specific burgee (a distinguishing flag, typically used by clubs or vessels).
- 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_69e73857784881908c3b8418a4c00c1e |
completed | April 21, 2026, 8:41 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:04 p.m.