Triple
T36619494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble B |
E903692
|
entity |
| Predicate | belongsToAstronomicalBody |
P165824
|
FINISHED |
| Object | Moon |
—
|
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: Moon | Statement: [Hubble B, belongsToAstronomicalBody, Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToAstronomicalBody Context triple: [Hubble B, belongsToAstronomicalBody, Moon]
-
A.
associatedWithCelestialBody
Indicates a relationship in which an entity has a connection, link, or relevance to a specific celestial body (such as a planet, star, or moon).
-
B.
hasCentralBodyRole
Indicates that an entity serves as the primary or central functional component within a larger body or system.
-
C.
isLagrangianSatelliteOf
Indicates that one celestial body occupies a Lagrangian point and thus functions as a gravitationally bound satellite associated with another primary body.
-
D.
orbitedBody
Indicates that one object moves in a path around another object due to gravitational or similar orbital forces.
-
E.
hasOrbitalRelationship
chosen
Indicates that one entity is in an orbital relationship with another, such as revolving around or being gravitationally bound in a regular orbit.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:11 p.m.