Triple
T32282500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy’s Rock |
E824737
|
entity |
| Predicate | explorationToolUsed |
P91992
|
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: [Tracy’s Rock, explorationToolUsed, Lunar Roving Vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorationToolUsed Context triple: [Tracy’s Rock, explorationToolUsed, Lunar Roving Vehicle]
-
A.
typeOfExplorationEquipment
Indicates that one entity is a specific kind or category of exploration equipment used for investigative or exploratory activities.
-
B.
explorationUse
Indicates the use of something specifically for exploration or investigative activities.
-
C.
usesExplorationMethod
Indicates that one entity employs or applies a particular exploration method as part of its process or behavior.
-
D.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
E.
usesToolFor
chosen
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
- 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_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:43 a.m.