Triple
T32282477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy’s Rock |
E824737
|
entity |
| Predicate | exploredDuringEVA |
P23375
|
FINISHED |
| Object | Apollo 17 EVA 2 |
—
|
NE NERFINISHED |
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: Apollo 17 EVA 2 | Statement: [Tracy’s Rock, exploredDuringEVA, Apollo 17 EVA 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploredDuringEVA Context triple: [Tracy’s Rock, exploredDuringEVA, Apollo 17 EVA 2]
-
A.
exploredDuring
chosen
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
B.
exploredByAstronaut
Indicates that something has been examined, traveled through, or investigated by an astronaut.
-
C.
hasExploration
Indicates that one entity engages in, is associated with, or possesses an activity or process of exploration in relation to another entity or context.
-
D.
crewEVAPlanned
Indicates that a spacewalk (extravehicular activity) involving crew members is scheduled or planned to occur.
-
E.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:43 a.m.