Triple
T37747574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 |
E940887
|
entity |
| Predicate | massOnLunarSurface |
P188995
|
FINISHED |
| Object | approximately 300 kilograms |
—
|
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: approximately 300 kilograms | Statement: [Surveyor 3, massOnLunarSurface, approximately 300 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massOnLunarSurface Context triple: [Surveyor 3, massOnLunarSurface, approximately 300 kilograms]
-
A.
massRelativeToMoon
Indicates that one entity’s mass is being expressed as a value relative to, or in comparison with, the mass of the Moon.
-
B.
massRelativeToEarth
Indicates the comparative amount of mass an entity has relative to the mass of Earth.
-
C.
isOnMoonOf
Indicates that one entity is located on, or positioned upon the surface of, a natural satellite (moon) that orbits another specified celestial body.
-
D.
lunarModuleMass
Indicates the mass or weight associated with a lunar module in the described context.
-
E.
numberLandedOnMoon
Indicates the count of distinct entities that have successfully landed on the Moon.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.