Triple
T34643611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 12 landing site |
E889635
|
entity |
| Predicate | purposeOfSelection |
P3364
|
FINISHED |
| Object | precision landing near Surveyor 3 |
—
|
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: precision landing near Surveyor 3 | Statement: [Apollo 12 landing site, purposeOfSelection, precision landing near Surveyor 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfSelection Context triple: [Apollo 12 landing site, purposeOfSelection, precision landing near Surveyor 3]
-
A.
selectionReason
chosen
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
purposeOfOffer
Indicates that an offer is made with the specific aim, intention, or objective of achieving a particular outcome or serving a particular function.
-
C.
purposeOfStudy
Indicates that one entity is the goal, aim, or intended objective motivating the conduct of a particular study.
-
D.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
E.
subjectChoice
Indicates that an entity makes, has, or is associated with a particular choice or selection among alternatives.
- 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.