Triple
T17805761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-210 sounding rocket |
E444552
|
entity |
| Predicate | originatedInProgram |
P17523
|
FINISHED |
| Object | Japanese sounding rocket program |
—
|
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: Japanese sounding rocket program | Statement: [S-210 sounding rocket, originatedInProgram, Japanese sounding rocket program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedInProgram Context triple: [S-210 sounding rocket, originatedInProgram, Japanese sounding rocket program]
-
A.
originProgram
chosen
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
D.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
E.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880385b48190b8dea0f05dfa1300 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.