Triple
T7771534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn V S-II second stage |
E179083
|
entity |
| Predicate | successorEngineTechnology |
P25950
|
FINISHED |
| Object | J-2S (test development only) |
—
|
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: J-2S (test development only) | Statement: [Saturn V S-II second stage, successorEngineTechnology, J-2S (test development only)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEngineTechnology Context triple: [Saturn V S-II second stage, successorEngineTechnology, J-2S (test development only)]
-
A.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
-
B.
successorEngineFamily
Indicates that one engine family directly follows and replaces another in a product or development lineage.
-
C.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
-
D.
laterUsedTechnology
chosen
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
E.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c7045ebae88190a04c8f972795e615 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.