Triple
T3668277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mysterium Cosmographicum |
E77814
|
entity |
| Predicate | planetaryCountConsidered |
P50044
|
FINISHED |
| Object | six known planets |
—
|
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: six known planets | Statement: [Mysterium Cosmographicum, planetaryCountConsidered, six known planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetaryCountConsidered Context triple: [Mysterium Cosmographicum, planetaryCountConsidered, six known planets]
-
A.
numberOfReportedPlanetCandidates
Indicates the count of planet candidates that have been reported or identified in a given context or dataset.
-
B.
hasNumberOfKnownMoons
Indicates the relationship that specifies how many moons are known to orbit a given celestial body.
-
C.
habitableZoneCandidates
Indicates that the related objects are potential locations or bodies situated within a region where conditions may allow habitability, such as supporting liquid water or life.
-
D.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
E.
numberOfMoons
Indicates the quantity of moons that an astronomical body possesses.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42997d88190bc765559bd7645fc |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:25 p.m.