Triple
T19831297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules Globular Cluster |
E476465
|
entity |
| Predicate | clusterShape |
P137491
|
FINISHED |
| Object | roughly spherical |
—
|
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: roughly spherical | Statement: [Hercules Globular Cluster, clusterShape, roughly spherical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusterShape Context triple: [Hercules Globular Cluster, clusterShape, roughly spherical]
-
A.
clusterConcentration
Indicates how densely the elements within a cluster are packed or distributed relative to one another.
-
B.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
C.
clusterStructure
Indicates that multiple entities are organized into a cluster, specifying how the elements are grouped and related within that clustered arrangement.
-
D.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
-
E.
arealCluster
Indicates that entities belong to the same spatially contiguous or closely grouped geographic area.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656ce68b48190aa25b29d0b6ea021 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.