Triple
T20973873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 1818 |
E516572
|
entity |
| Predicate | hasHighStellarDensity |
P131631
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NGC 1818, hasHighStellarDensity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighStellarDensity Context triple: [NGC 1818, hasHighStellarDensity, true]
-
A.
hasHighGalaxyDensity
Indicates that a region of space contains an unusually large number of galaxies per unit volume compared to typical cosmic environments.
-
B.
stellarDensity
chosen
Indicates the concentration of stellar objects within a given region of space, typically measured as the number of stars per unit volume.
-
C.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
-
D.
hasHighDensityOf
Indicates that one entity contains or exhibits a large concentration or amount of another entity within a given area, volume, or context.
-
E.
hasCentralStarType
Indicates that one entity (typically a planetary system) is associated with or characterized by a central star of a specified stellar type.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba2406c8190bd75dec585c14bfa |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:45 p.m.