Triple
T33732072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion |
E864298
|
entity |
| Predicate | carriedLunarRover |
P36763
|
FINISHED |
| Object | Lunar Roving Vehicle 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: Lunar Roving Vehicle 2 | Statement: [Orion, carriedLunarRover, Lunar Roving Vehicle 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedLunarRover Context triple: [Orion, carriedLunarRover, Lunar Roving Vehicle 2]
-
A.
usedLunarRovingVehicle
Indicates that an entity operated or traveled using a lunar roving vehicle during a lunar mission or activity.
-
B.
lunarRovingVehicleNumber
chosen
Indicates the identifying number assigned to a specific lunar roving vehicle in a mission or dataset.
-
C.
carriesLander
Indicates that one entity transports or holds a lander as its payload or cargo.
-
D.
lunarModuleCompanion
Indicates a relationship where one entity serves as a companion or partner to another in the context of a lunar module mission or activity.
-
E.
roverCountryOfOrigin
Indicates the country where a rover was originally designed, built, or first operated.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:44 a.m.