Triple
T34643532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 landing site |
E889633
|
entity |
| Predicate | gravitationalBody |
P27402
|
FINISHED |
| Object | Earth–Moon system |
—
|
NE NERFINISHED |
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: Earth–Moon system | Statement: [Surveyor 3 landing site, gravitationalBody, Earth–Moon system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitationalBody Context triple: [Surveyor 3 landing site, gravitationalBody, Earth–Moon system]
-
A.
centralBody
chosen
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
B.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
C.
cosmicBodies
Indicates a relationship in which entities are identified as astronomical or celestial objects existing in outer space.
-
D.
observedAstronomicalBody
Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
-
E.
orbitalBodyType
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72293e1188190b0c96f0d0bc0288e |
completed | May 3, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.