Triple
T10845588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intrepid |
E256000
|
entity |
| Predicate | lunarLandingSiteDetail |
P96028
|
FINISHED |
| Object | near Surveyor 3 landing site |
—
|
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: near Surveyor 3 landing site | Statement: [Intrepid, lunarLandingSiteDetail, near Surveyor 3 landing site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lunarLandingSiteDetail Context triple: [Intrepid, lunarLandingSiteDetail, near Surveyor 3 landing site]
-
A.
wasLandingSiteForAstronaut
Indicates that a particular location served as the landing site for an astronaut.
-
B.
lunarLandingRegion
Indicates the geographic region on the Moon where a spacecraft or mission has landed.
-
C.
lunarLandingCoordinates
Indicates the specific geographic location on the Moon where a landing event took place.
-
D.
keyLandingSite
Indicates a location that serves as the primary or designated site where something (such as a vehicle, object, or mission) is intended to land or touch down.
-
E.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:19 p.m.