Triple
T7722468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS |
E175046
|
entity |
| Predicate | usedInProgramPhase |
P44502
|
FINISHED |
| Object | operational Space Shuttle era |
—
|
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: operational Space Shuttle era | Statement: [STS, usedInProgramPhase, operational Space Shuttle era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProgramPhase Context triple: [STS, usedInProgramPhase, operational Space Shuttle era]
-
A.
usedByProgram
chosen
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
B.
laterUsedForProgram
Indicates that something is subsequently utilized as part of, or as input to, a program or programming process.
-
C.
usedProgramModel
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
D.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
E.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
- 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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:05 p.m.