Triple
T37747593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 |
E940887
|
entity |
| Predicate | componentReturnedToEarth |
P104366
|
FINISHED |
| Object | television camera |
—
|
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: television camera | Statement: [Surveyor 3, componentReturnedToEarth, television camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentReturnedToEarth Context triple: [Surveyor 3, componentReturnedToEarth, television camera]
-
A.
transportedToEarthBy
chosen
Indicates that an entity was moved or carried from another location or context to Earth by a specified agent or means.
-
B.
spacecraftReturn
Indicates that a spacecraft travels back from its mission location to its point of origin or designated return destination.
-
C.
leavesEarthWith
Indicates that one entity departs from Earth together with another entity, accompanying them in leaving the planet.
-
D.
removedFromEarthBy
Indicates that an entity was taken away or extracted from Earth by another agent or process.
-
E.
spacecraftRecoveryBy
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:19 p.m.