Triple
T5876375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-2 |
E130634
|
entity |
| Predicate | usedInConfiguration |
P19995
|
FINISHED |
| Object | cluster of five engines on Saturn V S-II |
—
|
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: cluster of five engines on Saturn V S-II | Statement: [J-2, usedInConfiguration, cluster of five engines on Saturn V S-II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInConfiguration Context triple: [J-2, usedInConfiguration, cluster of five engines on Saturn V S-II]
-
A.
usedInClusterConfiguration
chosen
Indicates that something is employed or referenced as part of the setup or parameters of a specific cluster configuration.
-
B.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
usedAsSettingFor
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
-
E.
usedInEnvironment
Indicates that something is utilized or operates within a particular environment or context.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.