Triple
T2706488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WASP-96b |
E59352
|
entity |
| Predicate | radiusRelativeToJupiter |
P42460
|
FINISHED |
| Object | larger radius than Jupiter |
—
|
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: larger radius than Jupiter | Statement: [WASP-96b, radiusRelativeToJupiter, larger radius than Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiusRelativeToJupiter Context triple: [WASP-96b, radiusRelativeToJupiter, larger radius than Jupiter]
-
A.
relativeSizeToEarth
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
B.
massRelativeToEarth
Indicates the comparative amount of mass an entity has relative to the mass of Earth.
-
C.
distanceFromEarthCenter
Indicates the measured or calculated spatial distance between an entity and the center of the Earth.
-
D.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
-
E.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda725f24819090e8d936b3d2d5bc |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:55 p.m.