Triple
T20264115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 5307 |
E498918
|
entity |
| Predicate | hasCentralStarVisibility |
P139457
|
FINISHED |
| Object | prominent |
—
|
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 | Statement: [NGC 5307, hasCentralStarVisibility, prominent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralStarVisibility Context triple: [NGC 5307, hasCentralStarVisibility, prominent]
-
A.
hasCentralStarType
Indicates that one entity (typically a planetary system) is associated with or characterized by a central star of a specified stellar type.
-
B.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
C.
numberOfCentralStars
Indicates the quantity of central stars associated with or contained within a given entity or system.
-
D.
isForegroundStarOf
Indicates that one star appears visually in front of another star along the line of sight, occupying the foreground relative to it.
-
E.
hasCentralGalaxy
Indicates that a galaxy cluster or group possesses a specific galaxy that occupies the central, dominant position within it.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674ce27688190b31d7a6c98d3ec5e |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:41 p.m.