Triple
T37217483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hercules Cluster |
E922779
|
entity |
| Predicate | hasAbellDistanceClass |
P187663
|
FINISHED |
| Object | distance class 4 |
—
|
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: distance class 4 | Statement: [Hercules Cluster, hasAbellDistanceClass, distance class 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbellDistanceClass Context triple: [Hercules Cluster, hasAbellDistanceClass, distance class 4]
-
A.
isDistantGlobularCluster
Indicates that one astronomical object is classified as a globular cluster located at a relatively large distance from the observer or reference point.
-
B.
hasAbellNumber
Indicates that a galaxy cluster is identified by and associated with a specific Abell catalog number.
-
C.
hasDistanceModulus
Indicates a relationship where a specific distance modulus value is associated with the separation between two entities or locations.
-
D.
hasApproximateDistanceFromEarth
Indicates that there is an estimated or non-exact distance between an entity and Earth.
-
E.
distanceInMegaparsecs
Indicates the physical separation between two entities measured in units of megaparsecs.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.