Triple
T20322127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-400 missile system |
E492230
|
entity |
| Predicate | deploymentTime_minutes |
P11880
|
FINISHED |
| Object | about 5 to 10 |
—
|
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: about 5 to 10 | Statement: [S-400 missile system, deploymentTime_minutes, about 5 to 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentTime_minutes Context triple: [S-400 missile system, deploymentTime_minutes, about 5 to 10]
-
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.
deploymentSpeed
Indicates how quickly a system, application, or component can be deployed from a ready state into a functioning production or target environment.
-
D.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
E.
deployedSince
Indicates that an entity has been deployed starting from a specific point in time and has remained in that deployed state since then.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.