Triple
T37588672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581d |
E935193
|
entity |
| Predicate | comparedToEarth |
P27811
|
FINISHED |
| Object | more massive than Earth |
—
|
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: more massive than Earth | Statement: [Gliese 581d, comparedToEarth, more massive than Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparedToEarth Context triple: [Gliese 581d, comparedToEarth, more massive than Earth]
-
A.
relativeSizeToEarth
chosen
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
B.
parentPlanetMassComparison
Indicates a comparison between the mass of a parent planet and the mass of another specified object or body.
-
C.
relationToEarth
Indicates the spatial, physical, or conceptual relationship that something has with Earth as a reference point.
-
D.
brightnessComparedToJupiter
Indicates how the brightness of one object compares to that of Jupiter.
-
E.
distanceFromEarth
Indicates the measured or calculated spatial separation between an entity and the planet Earth.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:18 p.m.