Triple
T29216550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perihelion |
E740681
|
entity |
| Predicate | hasAstronomicalReference |
P57107
|
FINISHED |
| Object | perihelion |
—
|
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: perihelion | Statement: [Perihelion, hasAstronomicalReference, perihelion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAstronomicalReference Context triple: [Perihelion, hasAstronomicalReference, perihelion]
-
A.
astronomicalBasis
chosen
Indicates that one entity serves as the astronomical foundation, reference, or underlying celestial cause for another entity or phenomenon.
-
B.
isAstronomicalObject
Indicates that something is classified as an astronomical object, such as a star, planet, moon, asteroid, or similar celestial body.
-
C.
hasAstronomicalCode
Indicates that an entity is associated with a specific astronomical identification code used in celestial catalogs or classification systems.
-
D.
hasAstrometricSource
Indicates that an entity is associated with a source providing astrometric measurements or positional data.
-
E.
hasSelenographicCoordinateSystem
Indicates that something is associated with or defined using a coordinate system based on the Moon’s (selenographic) latitude and longitude.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 12:13 p.m.