Triple
T33732114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 16 Far Ultraviolet Camera/Spectrograph |
E864299
|
entity |
| Predicate | locationOnMoon |
P138813
|
FINISHED |
| Object | Descartes Highlands |
E246520
|
NE 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: Descartes Highlands | Statement: [Apollo 16 Far Ultraviolet Camera/Spectrograph, locationOnMoon, Descartes Highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnMoon Context triple: [Apollo 16 Far Ultraviolet Camera/Spectrograph, locationOnMoon, Descartes Highlands]
-
A.
locatedOnSideOfMoon
Indicates that one entity is situated on a specific side or hemisphere of the Moon relative to another reference frame or viewpoint.
-
B.
isOnMoonOf
Indicates that one entity is located on, or positioned upon the surface of, a natural satellite (moon) that orbits another specified celestial body.
-
C.
isOnMoon
chosen
Indicates that one entity is physically located on the surface of the Moon.
-
D.
viewOnMoon
Indicates that an entity has a visual perspective or observable view from the surface or vicinity of the Moon.
-
E.
locationOnAstronaut
Indicates that one entity is located on the body or person of an astronaut.
- F. None of above.
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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e844f6c819098552979bd6db6b4 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:44 a.m.