Triple
T25734575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-7 engine |
E645339
|
entity |
| Predicate | designedForBody |
P9494
|
FINISHED |
| Object | Moon |
—
|
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: Moon | Statement: [BE-7 engine, designedForBody, Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForBody Context triple: [BE-7 engine, designedForBody, Moon]
-
A.
designedForComfort
Indicates that something has been intentionally created or configured to enhance physical or psychological ease and reduce discomfort.
-
B.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
bodyDesigner
Indicates that one entity is responsible for designing, shaping, or creating the physical form or structure of another entity.
-
D.
appliesToBodyType
Indicates that something (such as a rule, feature, or specification) is relevant or applicable to a particular body type.
-
E.
refersToBodyType
Indicates that one entity specifies, denotes, or is associated with a particular physical body type of another entity.
- 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_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 11:22 p.m.