Triple
T413178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas-Centaur |
E9534
|
entity |
| Predicate | notablePayload |
P7734
|
FINISHED |
| Object | Surveyor lunar landers |
—
|
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: Surveyor lunar landers | Statement: [Atlas-Centaur, notablePayload, Surveyor lunar landers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePayload Context triple: [Atlas-Centaur, notablePayload, Surveyor lunar landers]
-
A.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
B.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
C.
notableElement
chosen
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
D.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.