Triple
T11001031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon Impact Probe |
E260002
|
entity |
| Predicate | impactVelocity |
P13562
|
FINISHED |
| Object | approximately 1.6 km/s |
—
|
LITERAL FINISHED |
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: approximately 1.6 km/s | Statement: [Moon Impact Probe, impactVelocity, approximately 1.6 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactVelocity Context triple: [Moon Impact Probe, impactVelocity, approximately 1.6 km/s]
-
A.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
B.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
C.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
-
D.
speed
chosen
Indicates the rate at which an entity moves or changes position over time.
-
E.
impactTower
Indicates that one entity exerts a significant force or collision upon a tower-like structure, affecting its state or stability.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d68b608190a8d016b9383e82f8 |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.