Triple
T21884915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 418 |
E540379
|
entity |
| Predicate | hasCentralStarMagnitude |
P132320
|
FINISHED |
| Object | ~10.2 |
—
|
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: ~10.2 | Statement: [IC 418, hasCentralStarMagnitude, ~10.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralStarMagnitude Context triple: [IC 418, hasCentralStarMagnitude, ~10.2]
-
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.
centralStarApparentMagnitude
chosen
Indicates the apparent brightness (as seen from a given vantage point) of a system’s central star, expressed in astronomical magnitude.
-
D.
hasCentralStarVisibility
Indicates that the central star of an object or system is visible from a given viewpoint or under specified observational conditions.
-
E.
hasNoStarBrighterThanMagnitude
Indicates that, within a given set or system, there is no star whose brightness exceeds (is numerically less than) the specified magnitude threshold.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.