Triple
T23679063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CM-017 |
E584966
|
entity |
| Predicate | testedConfiguration |
P152962
|
FINISHED |
| Object | Block I Apollo command module |
—
|
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: Block I Apollo command module | Statement: [CM-017, testedConfiguration, Block I Apollo command module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedConfiguration Context triple: [CM-017, testedConfiguration, Block I Apollo command module]
-
A.
testedUnder
Indicates that one entity is examined, evaluated, or experimented on while being subject to the conditions, environment, or parameters specified by another entity.
-
B.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
C.
testedWith
Indicates that one entity has been examined, evaluated, or verified using another entity as the test method, tool, or counterpart.
-
D.
testedProcess
Indicates that an entity has performed a test or evaluation on a specific process.
-
E.
testedOn
Indicates that an entity has been used as the subject or material in a test, experiment, or evaluation performed by another entity.
- F. None of above. chosen
Provenance (4 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f5a7b48190b93d27416003e173 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.