Triple
T32282529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sculptured Hills |
E824738
|
entity |
| Predicate | visitedDuringEVA |
P26942
|
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: [Sculptured Hills, visitedDuringEVA, Apollo 17 EVA-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedDuringEVA Context triple: [Sculptured Hills, visitedDuringEVA, Apollo 17 EVA-2]
-
A.
visitedDuring
chosen
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
B.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
C.
visitedWith
Indicates that one entity visited a place or another entity together with a companion entity during the same occasion.
-
D.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
-
E.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
- 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_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:43 a.m.