Triple
T19278541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-48 |
E482120
|
entity |
| Predicate | UARSDeploymentTime |
P11880
|
FINISHED |
| Object | 1991-09-15 |
—
|
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: 1991-09-15 | Statement: [STS-48, UARSDeploymentTime, 1991-09-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UARSDeploymentTime Context triple: [STS-48, UARSDeploymentTime, 1991-09-15]
-
A.
deploymentTime
chosen
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
redeploymentTime
Indicates the amount of time required to redeploy or reassign a resource, system, or unit from one operational state or location to another.
-
C.
deployedSince
Indicates that an entity has been deployed starting from a specific point in time and has remained in that deployed state since then.
-
D.
deployedFor
Indicates that one entity is deployed or put into operational use to serve, support, or act on behalf of another entity.
-
E.
landerDeploymentDate
Indicates the date on which a lander is deployed or placed into its intended operational environment.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbe6e9c8190a7fa2ef3aa598e6c |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.