Triple
T9837501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar Seismic Profiling Experiment |
E239139
|
entity |
| Predicate | deploymentDate |
P41891
|
FINISHED |
| Object | December 1972 |
—
|
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: December 1972 | Statement: [Lunar Seismic Profiling Experiment, deploymentDate, December 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentDate Context triple: [Lunar Seismic Profiling Experiment, deploymentDate, December 1972]
-
A.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
C.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
D.
rolloutDate
Indicates the date on which something (such as a product, feature, or policy) is first introduced or made available for general use.
-
E.
landerDeploymentDate
chosen
Indicates the date on which a lander is deployed or placed into its intended operational environment.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.