Triple
T21348050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 2362 |
E526393
|
entity |
| Predicate | hasClusterCoreRadius |
P132951
|
FINISHED |
| Object | about 2 light-years |
—
|
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: about 2 light-years | Statement: [NGC 2362, hasClusterCoreRadius, about 2 light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClusterCoreRadius Context triple: [NGC 2362, hasClusterCoreRadius, about 2 light-years]
-
A.
hasClusterRadius
chosen
Indicates the radius or spatial extent associated with a particular cluster.
-
B.
hasCluster
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
-
C.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
D.
hasCorePopulation
Indicates that an entity possesses a central or primary group of individuals that constitute its main population.
-
E.
hasCoveringRadius
Indicates the maximum distance from any point in a space to the nearest point in a given set, defining how well that set covers the space.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad2d01b481909d9b4813ff37905c |
completed | April 22, 2026, 11:12 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:01 p.m.