Triple
T25734592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-7 engine |
E645339
|
entity |
| Predicate | designedForPrecision |
P17138
|
FINISHED |
| Object | precision lunar landing |
—
|
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: precision lunar landing | Statement: [BE-7 engine, designedForPrecision, precision lunar landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForPrecision Context triple: [BE-7 engine, designedForPrecision, precision lunar landing]
-
A.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
B.
calibratedFor
chosen
Indicates that something has been adjusted or tuned to operate accurately or optimally for a specific target, condition, or context.
-
C.
designedToMeasure
Indicates that one entity was intentionally created or configured for the purpose of quantifying, assessing, or evaluating another entity or its properties.
-
D.
exactFor
Indicates that one entity corresponds to or matches another entity with complete precision, without any deviation or approximation.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 11:22 p.m.