Triple
T6175244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praesepe |
E137800
|
entity |
| Predicate | tidalRadius |
P69244
|
FINISHED |
| Object | about 39 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 39 light-years | Statement: [Praesepe, tidalRadius, about 39 light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalRadius Context triple: [Praesepe, tidalRadius, about 39 light-years]
-
A.
tidalRadius_pc
Indicates the radius, measured in parsecs, within which an object (such as a star cluster or satellite) remains gravitationally bound before external tidal forces dominate.
-
B.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
C.
tidalDebris
Indicates material that has been gravitationally stripped from an astronomical object and dispersed into space by tidal forces.
-
D.
hasRadius_solarRadius
Indicates that an entity has a radius whose value is expressed in units of the Sun’s radius.
-
E.
coreRadius_ly
Indicates the radius of an object's core region measured in light-years.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.