Triple
T30023957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5189 |
E762827
|
entity |
| Predicate | hasCentralStarBinary |
P84325
|
FINISHED |
| Object | suspected |
—
|
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: suspected | Statement: [NGC 5189, hasCentralStarBinary, suspected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralStarBinary Context triple: [NGC 5189, hasCentralStarBinary, suspected]
-
A.
hasCompanionStar
chosen
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
B.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
C.
hasCentralStarType
Indicates that one entity (typically a planetary system) is associated with or characterized by a central star of a specified stellar type.
-
D.
hasSpectroscopicBinaryType
Indicates that an entity is classified as a spectroscopic binary of a specific type, based on characteristics observed in its spectrum.
-
E.
hasSecondBrightestStar
Indicates that one entity possesses or is associated with another entity that is the second most luminous star within a specified group or system.
- 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_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 6:48 p.m.