Triple
T32282437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Station 6 |
E824736
|
entity |
| Predicate | exploredUsing |
P100842
|
FINISHED |
| Object | Lunar Roving Vehicle |
—
|
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: Lunar Roving Vehicle | Statement: [Station 6, exploredUsing, Lunar Roving Vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploredUsing Context triple: [Station 6, exploredUsing, Lunar Roving Vehicle]
-
A.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
B.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
-
C.
exploredDuring
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
D.
explorationUse
chosen
Indicates the use of something specifically for exploration or investigative activities.
-
E.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
- 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_69f6bccc5be081908b121f4035b42dd9 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:43 a.m.